Plain fetch (Node / TypeScript)
The lowest-level integration. wrapFetchWithPayment intercepts the 402, signs the payment, and retries automatically.
Every endpoint on gateway.apiosk.com speaks x402. Your agent requests, the gateway replies 402 Payment Required with a price, your wallet signs a USDC payment on Base or Solana, and the data comes back. No API key, no account, no invoice.
Every example below uses a placeholder FX endpoint. Swap in any endpoint from the catalog at gateway.apiosk.com.
The lowest-level integration. wrapFetchWithPayment intercepts the 402, signs the payment, and retries automatically.
Same flow, for codebases already on axios.
The same pay-per-call flow for Python services, built on httpx and eth-account.
Expose an Apiosk endpoint as a tool your model can decide to call.
Wrap a paid endpoint as a LangChain tool your Python agent can call. Paid per call in USDC via x402. No API key required.
One config block gives your assistant the entire Apiosk catalog as tools.
Pick the surface that fits where your software runs. Same payment flow underneath, whether you reach for raw HTTP, a hosted MCP endpoint, the SDK, or the gateway skill.
The raw payment gateway. Handle the 402, attach an x402 proof, retry. Maximum control over headers, retries, and ledger events.
https://gateway.apiosk.com
A hosted MCP endpoint for chat-native agents. Add the URL, finish OAuth once, run paid tools from the same session.
https://mcp.apiosk.com/mcp
A package for application code that wraps payment execution, typed 402 errors, and retry helpers for Node backends.
npm install @apiosk/sdk
An installable skill for coding agents like Claude Code and Codex that need to run paid gateway requests from a shell.
npx skills add Apiosk/openclaw-apiosk --skill apiosk-gateway
List it as it is, or keep your own URL and let the SDK put the paywall there.
Managed listing. No code changes.
@apiosk/sdk in front of your routes.
Agents pick, call, pay per request.
One script tag on a page the agent already reads. It discovers the endpoint, gets the price, pays and calls without ever leaving your docs. Your API stays unchanged. Apiosk handles the payment and grants access after it.
Agents buy straight from your docs, on your domain.
The same listing is where agents shop for tools.
Auto-registered in Coinbase's x402 Bazaar.
Fund it with a few USDC and give your client a private key it can sign with. Payments settle on Base.
Every snippet below runs on a current Node or Python runtime. Pick the stack you already ship on.
Each 402 response states the exact price up front. Nothing is charged without your client signing it.
Every settled call produces an on-chain receipt on Base. Set per-transaction and per-day caps in your wallet mandate so an agent loop can never drain funds.
Questions, or a missing endpoint you want listed? Email hello@apiosk.com.
No. Every endpoint on gateway.apiosk.com speaks x402. Your agent makes a request, the gateway replies 402 Payment Required with a price, your wallet signs a USDC payment on Base or Solana, and the data comes back. There is no API key, no account, and no invoice.
A helper such as wrapFetchWithPayment (fetch), withPaymentInterceptor (axios), or the x402HTTPXClient (Python) intercepts the 402 response, signs the payment with your wallet, and retries the request automatically. You call the endpoint as you normally would and get the data back.
Node and TypeScript via x402-fetch and x402-axios, Python via x402-httpx and eth-account, agent frameworks via the Vercel AI SDK and LangChain, and any MCP client (Claude Desktop, Claude Code, Cursor) via the hosted MCP endpoint.
Set spend caps per transaction and per day in your wallet mandate. The exact price is stated in every 402 response before payment, nothing is charged without your client signing it, and every settled call produces an on-chain receipt on Base you can verify independently.
Built for APIs, MCP servers, datasets and digital services.