Plain fetch (Node / TypeScript)
The lowest-level integration. wrapFetchWithPayment intercepts the 402, signs the payment, and retries automatically.
Connect through MCP or API. Discover services, review prices and run the work you approve.
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.
The same paid call, written the way each framework expects it: the tool definition, the wallet, and the agent run.
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
Everything about listing a service, what the provider dashboard does and how the money reaches you is on its own page now.
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.
Apiosk helps people and AI agents get data from paid APIs. Describe what you need, review the proposed service or research plan and its price, then approve the work. Apiosk handles the calls and returns the available results with their sources.
Answer helps with a direct data request, such as a company profile or filed accounts. Research creates a plan for requests that need several steps. It can resolve a company first and use that identity to retrieve its records. The plan shows what it can cover before you approve.
Apiosk asks for context when it needs a company, location, period or other detail. If a provider does not have the requested data, the result should say what is missing. Data availability depends on the source; an API listing does not guarantee that every record exists.
The price depends on the services your request needs. Apiosk shows the total, including its service fee, before you approve. You pay per use from your balance, with no subscription required.
See pricingNo. In the Apiosk app, you ask in ordinary language and approve the price. You do not need a separate API key or account for each provider. Developers can also connect through MCP or API.
Yes. Apiosk is available as a connector for ChatGPT and Claude, and through MCP for other agents and tools. Connect once, sign in to Apiosk, and ask your question from there. The price is shown before anything runs and is paid from your Apiosk balance.
Connect an agentYes. Connect a compatible agent through MCP or API and authorize its access to your Apiosk account. Spending limits and approval rules control what it can buy.
Connect an agent