updated 2026-10-30 · on-chain data complete since 2025-05-09
The State of x402
A live, data-driven map of the entire x402 payment ecosystem.
We continuously probe every listed x402 endpoint and watch every USDC
settlement on-chain (Base + Solana). The headline: of 361,151 listed endpoints,
63% are unreachable, 4% of the reachable ones serve a
non-compliant payment envelope, and only 40% of the pay-to
wallets behind them have ever received a payment. The directory is mostly ghosts.
The ecosystem right now
123,040,811 probes and counting37%
actually reachableof 294,765 active endpoints
96%
spec-compliant 402of the reachable ones
40%
wallets ever paid5,607 earning wallets
361,151
endpoints listed
294,765
currently active
66,386
delisted
123,040,811
probes executed
Real money settled (on-chain)
$56.90M
total volume
255,903,584
settlements
207,454
paying wallets (tracked)
5,607
wallets that ever earned
Total volume is measured across all known x402 facilitators: every USDC settlement one of them submitted on-chain (Base + Solana). Coverage depth: Base is complete since May 2025; Solana history starts at each facilitator address's registry date (deep-history windows for the largest Solana facilitators were backfilled 2026-08-26; long-inactive tail addresses may start later). Per-facilitator market share: the facilitator leaderboard. Per-wallet figures below (top earners, paying wallets) cover the 5,607 distinct pay-to wallets we resolve to a listed endpoint; one seller often runs many endpoints off a single wallet.
Monthly momentum
▲ +0.9% 2026-09 vs 2026-08
Where the money goes (top earners)
click a column to sort| # | endpoint▼ | volume▼ | share▼ | settlements▼ | payers▼ |
|---|---|---|---|---|---|
| 1 | 5yASLj…NgRn (unlisted) | $1.79M | 47.9% | 6,388 | 1,053 |
| 2 | api.bitrefill.com | $555K | 14.9% | 5,786 | 1,060 |
| 3 | 3MZVk9…NfYX (unlisted) | $406K | 10.9% | 1,275 | 358 |
| 4 | FPfGD3…7Vk4 (unlisted) | $205K | 5.5% | 250 | 69 |
| 5 | api.surplusintelligence.ai | $151K | 4.1% | 35,088 | 25 |
| 6 | swarmx.io | $96K | 2.6% | 3,377 | 23 |
| 7 | agentapi.rozo.ai | $76K | 2% | 642 | 5 |
| 8 | api.slamai.dev | $44K | 1.2% | 275 | 22 |
| 9 | api.vapinetwork.ai | $42K | 1.1% | 167 | 25 |
| 10 | GptpyP…Rhez (unlisted) | $39K | 1% | 83 | 22 |
What's broken (402 envelope issues, 30d)
no-envelope7,375,960no-accepts6,117,303missing-x402-version6,068,944http-status-5025,903,774http-status-4043,271,863http-status-5031,043,549http-status-200797,396http-status-400516,336http-status-410234,875missing-resource-info230,156HTTP-native vs MCP-native
reliability split by probe transport
HTTP-nativeplain HTTP 402 paywall
294,408
active endpoints · 99.9%
54.8%
avg uptime (scored)
A · 30,501 B · 70,822 C · 12,455 D · 3,236 F · 87,210 ? · 90,184
MCP-nativex402 challenge served over MCP
357
active endpoints · 0.1%
62.8%
avg uptime (scored)
A · 9 B · 154 C · 41 D · 19 F · 98 ? · 36
MCP-native services never answer a bare HTTP request with a 402: the challenge only appears after an MCP handshake (
initialize → tools/list → an unpaid tools/call). We probe both paths without ever paying and grade the payment envelope identically, so the two populations are directly comparable. MCP probe latency includes the handshake and is not 1:1 comparable to HTTP latency.Where endpoints are listed
discovery sources over active endpoints; one endpoint can appear in severalx402scan186,664bazaar119,461thirdweb91,050payai24,428ultravioletadao7,019threews4,817dexter3,204manual1,551openfacilitator323mcpregistry304anyspend18customer4found on x402scan found on CDP Bazaar found on thirdweb found on PayAI found on Ultravioleta DAO found on three.ws found on Dexter manual submission found on OpenFacilitator MCP registry found on AnySpend customer referral