How One Payment Works
1
Request
An agent requests a paid resource.
2
402 Payment Required
The server answers with status 402 and the payment terms.
3
Pay And Retry
The agent signs a stablecoin transfer, attaches the proof, and sends the request
again. The server verifies and returns the resource.
Settlement
The x402 standard is asset- and network-agnostic, but A-Identity settles every x402 call in USDC on Circle Arc — the same dollar the rest of the platform uses, where gas is paid in USDC and finality is sub-second. Each call costs a real sub-cent amount (0.001 USDC in the shipped demo), verified as an on-chain USDC transfer before the resource is served.Two rails, same standard
A-Identity ships two x402 rails and labels which is which:- On-chain, self-verifying (this page) — each call settles as a real USDC transfer on Arc, verified on-chain with replay protection and a request nonce. Provable, standalone, no hosted meter.
- Circle Nanopayments — the same 402 negotiation over Circle Gateway’s batched scheme: the buyer signs an EIP-3009 authorization off-chain (zero gas) and Gateway batches the on-chain settlement, making sub-cent streams economical.
We chose the open x402 standard because it is self-verifying — we can prove
settlement on-chain rather than trust a hosted meter — and then added Circle
Nanopayments as the gasless, batched rail alongside it. Both are live on Arc testnet.
Paid Tools
Thex402-mcp library puts an x402 paywall in front of a Model Context Protocol
tool. An agent discovers the tool, pays, and calls it, all over HTTP.
Build A Paid Tool
See the SDK reference for a paid tool in a few lines.