Set up
Give your agent the ability to buy
Two routes, one balance. Point a runtime at the hosted skill, or add the MCP server to your client — either way the agent discovers what can do a job, sees the price before it spends, and pays out of credit you topped up yourself.
Step 1
Choose your setup
The skill is a document your agent reads. The MCP server is a set of tools your client calls. Runtimes that support both work fine with either — pick the one your client already understands.
Give your agent the URL
Any runtime that reads Agent Skills can be pointed straight at the document. It is plain Markdown, it is public, and it holds no credential — so it can be pasted into a chat, committed to a repository or put in a system prompt without anybody having to think about what is in it.
https://apiosk.com/skill.mdThe agent reads it and knows how to discover an API, price a call and run it. The five reference documents it points at are published beside it, so nothing has to be downloaded first.
Prefer a folder on disk? The app builds the same skill as a zip for your runtime, with its install path on the card. Connect an agent.
Add the server to your client
Works with Claude Code, Codex, Cursor, Gemini CLI, VS Code and anything else that speaks MCP. Discovery, comparison and the decision are free and need no account — only running a call spends anything.
https://mcp.apiosk.com/mcpclaude mcp add -s user --transport http apiosk https://mcp.apiosk.com/mcpThen sign in from inside the client — /mcp in Claude Code — which is the step that ties the server to your balance. The per-client commands for the other eight are in the app, where they are kept in step with the server itself: Connect an agent.
Step 2
Connect it to your balance
Discovery, comparison and the decision are free and anonymous — an agent can price a job before it has any credential at all. Running a call spends money, and that needs a connection.
Your agent asks
It requests a connection and says what it is and what it is for. Nothing is granted yet, and it never asks you for a password or a token — there is nothing it could do with one.
You approve it
One screen in Apiosk, showing what the agent claimed and the ceilings you are about to set: the most it may spend on a single call, and the most in a rolling day.
It holds its own credential
The agent receives a token it renews by itself. There is nothing for you to copy, store or rotate, and revoking it is one click on the same screen.
What the agent reads
The document is public
Nothing in the skill is secret, which is why it can be served at one address to everybody. It carries no token, no invitation and no account — the private half of the flow is the approval above, and it happens in your browser.
The skill itself
What an agent is told: how to describe a job, read the prices that come back, choose one and run it.
apiosk.com/skill.mdConnecting
Read by an agent that has no access token yet. One question to you, one request, and it is connected.
apiosk.com/skill/references/connecting.mdTroubleshooting
Every status the gateway can answer with, what it means, and what the agent should do about it.
apiosk.com/skill/references/troubleshooting.mdTop up once. Every API on the other side.
No provider accounts, no per-vendor invoices, no keys to rotate.