Home/Buy-side
buy-side · for agent builders

Pay APIs from your AI agent in 30 seconds.

No account. No API key. No SDK required. Your agent sends a request, gets back a 402 quote, signs a USDC transfer on Base, retries with the receipt header. Five lines of bash if you want the minimum. the catalog across 7 categories — documents, audio, images, web, validation, conversions, plus 10 agent-native primitives.

Endpoints
157first-party
From
$0.0001/ call
Settle
~1.2 son Base
Runtimes
7SDKs official
why x402

HTTP that finally pays itself.

Every API on the market today assumes a human registers, files a card, and watches a dashboard. Your agent doesn't. HTTP 402 is the wire protocol that gives APIs a way to charge per call without a human in the loop. USDC on Base settles atomically in ~1.2 s. Five lines of curl plus a transaction is the whole client.

Five lines of curl + USDC.transfer() is the minimum viable client. No SDK is mandatory. The wire protocol is the contract.

quickstart · 3 steps

From zero to 200 OK.

01
Fund a Base walletAny wallet with USDC on Base. $1 = roughly 2 000 trivial calls or 100 vision captions.
~30 s
02
Hit an endpoint, receive a 402 quotePOST your payload. Receive 402 Payment Required with EIP-712 signed quote (amount, asset, payTo).
402
03
Pay on Base, retry with X-PaymentSign the USDC transfer, include the receipt as X-Payment header. Receive 200 OK + your JSON.
200 · JSON
bash · the whole flow
# 1 — quote
curl -i -X POST https://api.tools402.dev/v1/pdf-md \
     -F "file=@receipt.pdf"

HTTP/1.1 402 Payment Required
{ "maxAmountRequired": "10000", "payTo": "0xD6E8…2878" }

# 2 — pay on Base
cast send 0x833589fCD…2913 \
     "transfer(address,uint256)" \
     0xD6E8…2878 10000 \
     --rpc-url https://mainnet.base.org

✓ tx 0x4f02… · 1 confirm · ~1.2 s

# 3 — retry
curl -X POST https://api.tools402.dev/v1/pdf-md \
     -H 'X-Payment: eyJ4NDAyVi…ifQ' \
     -F "file=@receipt.pdf"

HTTP/1.1 200 OK
{ "markdown": "# Receipt …" }
7 runtimes · pick yours

Drop into the runtime your agent already speaks.

Same wire protocol behind each. Each official package handles 402 → pay → retry, signing, idempotent retries, and 60-second timeout recovery.

cost calculator

How much does your agent cost to run?

Slide the knobs. The number on the right is what you'd pay per month, settled atomically on Base. Compare against a typical Twilio + Clearbit + GPT API setup.

5 000
Light
30

tools402 per-call

$22.50
/ month · no minimum · settled atomically
Typical Twilio + Clearbit + GPT API setup for the same workload: $180 / month + setup time.
the moat · multi-facilitator

Never goes silent.

When Coinbase facilitators went silent for 25 days in January 2026, we didn't. Multiple x402 facilitators run in parallel — Coinbase CDP / PayAI / local-key signer per chain — with sub-500 ms automatic failover. Buyer payment is live on Base, Polygon, and Solana. See /proof for the live runtime list.

Our proprietary routing engine — 105 tests, 100 % coverage, battle-tested in production — is the operational moat.

faq

Common questions.

Do I need a wallet on Base mainnet?
Yes. Any EVM-compatible wallet that can sign USDC transfers on Base works (MetaMask, Rabby, Coinbase Wallet, viem privateKeyToAccount, eth_account, etc.). Funding cost: gas is ~$0.005 per transfer.
What if my call fails after payment?
Payment is verified on the request, not the response. If the compute fails after settlement, the call is retried with the same X-Payment for up to 60 seconds. Persistent 5xx returns the tx hash in headers — auditable on Basescan. No off-chain refund mechanism by design.
Are there free trials or rate-limited free tiers?
No. Per-call pricing is the same for everyone. Meta endpoints (/v1/_meta, /v1/_health, /v1/_audit) are free. The fastest way to test is to fund $1 of USDC and run a real call — that's ~2 000 trivial calls of runway.
Can I use tools402 from outside an AI agent?
Yes. tools402 is just HTTP. Anyone who can sign a Base transfer can call it from curl, Postman, a CI pipeline, a backend service, an iOS app — the protocol doesn't care about the client.
Does it work with Google AP2 mandates?
Yes. 3 of 4 AP2 touchpoints are live (E2 MCP descriptor, E5 X-AP2-Mandate-Accepted response header, E9 POST /v1/agent/identity). See /docs/ap2 for build / verify examples.
What about privacy?
We don't log request bodies. The only persisted artifacts are the on-chain tx (public anyway) and a hashed correlation ID for idempotency (30-day TTL). PII passes through tools402 in transit only.
go

Make your first paid call in 5 minutes.

$1 of USDC = ~2 000 trivial calls of runway. Pick an endpoint, copy the curl, watch the 402. Settle once, see your tx on Basescan, retry with the receipt.