More APIs now sell to AI agents per call. The agent asks, the server answers HTTP 402 Payment Required with an offer, the agent pays a few cents in USDC and gets the result. That's x402. It's fast and needs no account, which also means your agent may be about to pay a server nobody has checked.
The good news: a 402 offer tells you a lot before any money moves.
What's in the offer
curl -i -X POST https://example-api.com/paid-route
The PAYMENT-REQUIRED header (base64 JSON) lists:
- payTo: the wallet that gets paid. Does it match the seller's published address?
- network and asset: for example Base and USDC. An unexpected token is a red flag.
- amount: the exact price in the asset's smallest unit. Check the decimals.
- resource: what you're buying. It should be the route you called.
What it doesn't tell you
Who runs the server, whether it will deliver, and whether the wallet is really theirs. For that you need checks outside the offer: is the domain live and real, does it publish the same wallet elsewhere, does it have a track record.
A free way to check
pageverified.com/check/x402 reads an x402 offer and explains it field by field, with no key or signup. There are matching free checks for MCP servers (/check/mcp) and agent readiness (/check/agent-readiness).
For agents, the same checks run as paid tools with no API key; a pre-pay check is 5 cents in USDC through x402 itself.
The rule we use
Never let an agent pay an endpoint whose payTo, network or amount you haven't seen and agreed to. The 402 is right there. Read it first.
Top comments (0)