Facilitators
Who relays and gas-sponsors x402 payments, derived on-chain. A facilitator submits the settlement transaction and pays its gas, which is what makes an x402 payment free of native tokens for the agent making it.
Roundhouse facilitator
Point your paywall or your client at ours and your payers need USDC only — no ETH, no top-up step. It serves Base mainnet, which the public x402.org facilitator does not. What it changes on top of that is what we can tell you afterwards.
https://x402.roundhouseai.io
- See which endpoint earned it. Settlements we relay carry the resource that was paid for. Read off the chain alone a payment is a bare USDC transfer, so a wallet serving forty endpoints is one line — through ours, each endpoint gets its own revenue, price and traffic.
- Know your customers, not their addresses. Every payer is resolved to an identity where one exists, and the endpoint they bought is attached to it — so repeat buyers, what each of them spends and which service brought them back are all answerable.
- Be named across the index. Your service appears as itself: a named route on the flow graph instead of “route unknown”, and a merchant page listing your endpoints rather than an unattributed wallet.
- Failures stay visible. Every verify and settle attempt is captured, successful or not, so a payment that never landed on-chain is still diagnosable. No chain indexer can do that — there is nothing on the chain to find.
Settlements relayed per day, by facilitator
Last 90 days- Coinbase CDP
- PayAI
- Daydreams(too small to plot)
- Heurist(too small to plot)
- FluxA
- Virtuals Protocol(too small to plot)
3 of these 6 operators settle too little to register against the busiest one, so they do not appear in the plot above. Their figures are in the table.
| Operator | Settlements | Settled | Buyers |
|---|---|---|---|
 Coinbase CDP | 24.58M | $1.14M | 30.20K |
 PayAI | 108.85K | $57.10K | 6,322 |
 Daydreams | 2,029 | $2278.93 | 159 |
 Heurist | 3,025 | $32.94 | 77 |
 FluxA | 1.01M | $205.68K | 7,466 |
 Virtuals Protocol | 1,474 | $29.86 | 264 |
The 6 operators that have relayed the most transactions, one colour each, per UTC day. The busiest relays several orders of magnitude more per day than the quietest, so the smallest operators cannot register against it on a shared scale and the legend says which those are — read them from the table, where each row carries that operator's own window totals across its whole relayer pool. There is no network-wide total anywhere here, in the table or on the hover, because site-wide aggregates live on /stats. A quiet stretch here is usually unresolved attribution, not a quiet network: a settlement joins an operator's series only once the pass that reads the relayer off the transaction has reached it, and that runs newest-first — so older settlements sit under “route unresolved” in the route breakdown until it catches up.
Every other facilitator
30 named operators| Facilitator | Wallets | Txs relayed | Share (est) | Payers | Last seen |
|---|---|---|---|---|---|
Named operators | |||||
| Coinbase CDP | 32 | 84,883,847 | 70.8% | 74 | 3h ago |
| PayAI | 5 | 17,396,132 | 8.0% | 1 | 2d ago |
| Daydreams | 2 | 13,026,193 | — | — | 2d ago |
| Heurist | 8 | 8,167,364 | — | — | 1d ago |
| FluxA | 6 | 2,010,741 | 11.4% | 19 | 1d ago |
| Virtuals Protocol | 1 | 1,997,261 | — | — | 1d ago |
 x402.rs | 6 | 995,030 | — | — | 2d ago |
 OpenX402 | 2 | 576,507 | — | — | 2d ago |
 AnySpend | 1 | 524,580 | 0.1% | 1 | 2d ago |
 CodeNut | 4 | 478,063 | — | — | 1d ago |
 Questflow | 10 | 474,767 | — | — | 1d ago |
 AurraCloud | 3 | 235,506 | — | — | 2d ago |
 Thirdweb | 1 | 135,526 | — | — | 3d ago |
 RelAI | 1 | 90,444 | 0.6% | 5 | 2d ago |
 Meridian | 1 | 84,597 | 0.2% | 2 | 3d ago |
 Dexter | 1 | 83,295 | — | — | 3d ago |
 Polymer | 1 | 55,376 | 0.1% | 1 | 2d ago |
 Primer | 1 | 36,589 | 0.3% | 4 | 1d ago |
 Cascade | 1 | 33,554 | 1.1% | 2 | 1d ago |
 Ultravioleta DAO | 1 | 25,420 | — | — | 2d ago |
 Mogami | 1 | 23,727 | — | — | 2d ago |
 Corbits | 1 | 19,778 | — | — | 1d ago |
 OpenFacilitator | 1 | 18,888 | — | — | 1d ago |
 xEcho | 1 | 12,232 | — | — | 2d ago |
 x402 Jobs | 1 | 7,982 | — | — | 1d ago |
Attribution comes from the open facilitator registry, which names 31 of the operators we have observed relaying settlements; the rest are relayer wallets seen on-chain with no operator behind them yet. Txs relayed is the wallet pool's on-chain transaction count (a fact); payers and share come from sampled 30-day discovery windows (estimates).
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will compare the facilitators that could settle your payments over the free read API. No key, no account.
GET api.roundhouseai.io/v0/facilitators
Show the promptHide the prompt
Using Roundhouse, compare the x402 facilitators: who relays the most settlements, which chains they serve, and which one I should use to start paying endpoints. curl -s 'https://api.roundhouseai.io/v0/facilitators' Then show me how to settle a payment through one: https://roundhouseai.io/docs/guides/use-the-roundhouse-facilitator The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.