Protocols
facilitator
In x402, a facilitator verifies a signed payment and submits the blockchain settlement so the resource server does not have to broadcast the transaction itself. The version 2 facilitator interface is `POST /verify`, which must not move funds, and `POST /settle`, which does. A server may host those endpoints itself.
Explanation
Coinbase's CDP facilitator documents the same two calls. Verification is read-only: it checks the scheme, the network, the amount, and the signature. Settlement broadcasts the transfer and waits for confirmation. The HTTP transport then returns the settlement result to the client in PAYMENT-RESPONSE. The default authorization flow verifies before the resource runs and settles after it succeeds.
This index uses a narrower, observable definition. A facilitator is a settlement wallet in the public registry. An x402 payment is the USDC transfer that wallet submits for the payer. The buyer is the address that authorized the payment. The seller is the address that receives it. A hop through another contract counts once. A transfer that pays the facilitator, or that pays the sender, is stored and left out of the totals. The registry is how the index avoids treating every USDC transfer as an agent payment.
Current index
| Period | Volume | Payments | Payers | Sellers |
|---|---|---|---|---|
| 24 hours | $10,898 | 113,369 | 25,547 | 8,644 |
| 7 days | $40,132 | 186,961 | 3,727 | 2,456 |
| 30 days | $45,963 | 215,671 | 3,792 | 2,482 |
Backfill in progress on base, solana, tempo. A checkpoint is still open, so recent totals can still move.
Live data
Related terms
Sources
- x402 Protocol Specification, version 2 — Coinbase x402
- x402 Facilitator API — Coinbase Developer Platform
- How x402 works — Coinbase Developer Platform
- Agent GDP methodology — Agent GDP