Pay-per-call APIs for software that buys for itself.
No accounts. No invoices. No humans in the loop.
Who's asking?
I'm a person
You want to understand what ApiToll is and whether to build with it.
↓I'm an agent
You want the integration payload. Curl, discovery endpoints, x402 flow.
→Agents reading this page directly can also jump to /llms.txt or /.well-known/mcp.json.
For agents
Load one skill. Buy any data we sell.
Drop our skill into Claude, Cowork, or any agent that reads markdown skills. Then ask in natural language — the agent picks the right service, signs the payment, and returns the answer.
1. Load this URL
https://apitoll.io/skill/SKILL.md
2. Ask anything we offer
“EUR/USD rate?”
“Geolocate 8.8.8.8”
“Holidays in Japan 2026”
3. Done
Wallet, payment, and on-chain settlement all handled. You get the answer.
What this is
A toll road for data.
ApiToll is an HTTP gateway where every request carries a price in USDC — set by the data provider, anything from a sub-cent micro-lookup to dollars per call for high-value data. The client opens a URL, the server returns 402 Payment Required with a signed quote, the client's wallet signs an authorization, the request is retried, the server verifies the payment on-chain and serves the data. Total time: about two seconds.
There is no signup. No API key. No monthly plan. No dashboard to log into. The wallet address is the identity. The settlement is the receipt.
This is the x402 protocol, the HTTP status code reserved decades ago for machine-to-machine payment that finally has rails beneath it.
The flow
Four steps. Two seconds.
-
Agent makes an ordinary GET request.
No headers. No credentials. Just a URL.
-
Server replies with HTTP 402 and a signed quote.
Amount, asset, treasury address, nonce, expiry. Everything the wallet needs to sign.
-
Wallet signs an EIP-3009 authorization. No gas in your wallet.
The authorization goes back in a single
X-PAYMENTheader. The agent never holds ETH. -
Server verifies, settles on Base, returns the data.
Revenue is recognized at the moment of service. The on-chain transfer is the audit trail.
Available now
Catalog.
Five live, more in development. Every endpoint is priced per call in USDC on Base.
BIN Lookup live
Card-issuer metadata for any 6-to-8-digit BIN prefix. Scheme, type, issuing bank, country.
FX Rates live
Daily ECB reference rates. 30+ base currencies, last refreshed every weekday at 16:30 UTC.
Country Data live
ISO-3166, ISO-4217, E.164 dialling codes, timezones, capitals. Resolve from name, code, or alias.
Public Holidays live
Public, bank, and regional holidays for any country and year. Sourced from date-holidays.
IP Geolocation live
City, ASN, and coordinates for IPv4 / IPv6. Powered by MaxMind GeoLite2.
For data providers
Got a dataset? Ship it as a toll.
You provide the endpoint and the per-call price. We provide the payment rails, the agent discovery, the ledger, the reconciliation, and on-chain payouts in USDC on Base mainnet. You keep the revenue minus a transaction fee that covers infrastructure and gas.
There are no invoices, no net-30 terms, no account managers. If you have ever wanted to monetize data without also building an auth system, a billing system, a dashboard, a dunning flow and a sales team, this is that.
Why it matters
Human auth does not fit machines.
When software agents transact with each other, the tools we built for humans start to break. You cannot make a bot sign up for an account. You cannot ask it to accept terms of service. You cannot rotate its API keys on a schedule designed for human calendars.
Agent-to-agent commerce needs four things that traditional APIs do not provide: identity without email, consent per call, deterministic settlement, and machine-readable discovery. x402 gives all four.
ApiToll is the operator's take on what the resulting economy looks like when it is actually wired up.