Documentation
The simplest way to understand Apiosk: an agent pays for one API call, gets the response, and moves on.
What Apiosk is
Apiosk is a pay-per-request API gateway for AI agents. It lets an agent buy access to an API call at the moment it needs it.
The access mechanism is simple: the gateway returns a 402 payment requirement, the agent signs the payment, retries the request, and gets the response.
This is the core wedge: agents paying for APIs without API keys or subscriptions.
One request, one payment
Every API call has a visible price. The agent pays only for the request it wants to make.
No API keys
Agents use wallet-based payment proofs instead of managing credentials across providers.
Built for live demos and real usage
The flow is simple enough to explain on stage and solid enough to run in production.
First Paid Call
The only story that matters is: pick a priced API, pay for one request, and show the result live.
Pick a live API
Choose an endpoint from Explore and note the exact per-request price.
Trigger the 402 challenge
Send a request without payment and let the gateway return the payment requirements.
Attach payment and retry
Your agent signs the payment proof, resends the request, and receives the response.
// 1. Request without payment
const first = await fetch("https://gateway.apiosk.com/weather/current?city=amsterdam");
// 2. Gateway returns 402 with payment requirements
if (first.status === 402) {
const requirement = await first.json();
// 3. Sign payment with your wallet and retry
const second = await fetch("https://gateway.apiosk.com/weather/current?city=amsterdam", {
headers: {
"X-Payment": "<signed payment proof>",
},
});
const result = await second.json();
console.log(result);
}Agent Flow
Apiosk is designed for agents that need utility APIs during runtime: weather, prices, company lookup, news, geocoding, and similar data or task endpoints.
The implementation model is straightforward. Your agent needs a wallet, a small USDC balance, and an x402-aware client. From there, payment becomes part of the request flow rather than a separate business process.
Why this is solid
- checkAgents do not need pre-issued credentials from every provider.
- checkProviders can expose paid access without building subscription billing.
- checkThe buyer sees the unit price before paying.
- checkThe demo maps directly to a real production workflow.
For Providers
Providers use Apiosk to turn an existing API into a priced endpoint for agents. The provider story is important, but it is still subordinate to the core buyer story: the first paid call.
What providers do
Register an API, set a price, route traffic through Apiosk, and track paid usage.
Why it matters
It creates an investable two-sided story: agent demand on one side, monetizable APIs on the other.
FAQ
What does Apiosk do?
Apiosk gives AI agents a wallet-native way to buy API access per request. Providers set prices, agents pay only for the calls they make.
Why is this better than API keys?
API keys force agent builders to pre-negotiate access with every provider. Apiosk replaces that with priced access at the point of use.
What is the demo story?
An agent selects a priced endpoint, gets a 402 payment requirement, signs the payment, retries the call, and receives the result.
Do providers need to rewrite their API?
No. Providers keep their existing API and place Apiosk in front of it to handle pricing, payment verification, and routing.
What does the agent need?
An EVM wallet, USDC on a supported network, and a client that can handle the x402 payment flow.
Who is this for right now?
Teams building AI agents that need utility APIs at runtime, and providers who want to monetize those calls without subscriptions or manual billing.