updated 2026-10-17 · 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 264,723 listed endpoints,
61% are unreachable, 4% of the reachable ones serve a
non-compliant payment envelope, and only 62.5% of the pay-to
wallets behind them have ever received a payment. The directory is mostly ghosts.
The ecosystem right now
112,360,221 probes and counting39%
actually reachableof 211,198 active endpoints
96%
spec-compliant 402of the reachable ones
63%
wallets ever paid5,034 earning wallets
264,723
endpoints listed
211,198
currently active
53,525
delisted
112,360,221
probes executed
Real money settled (on-chain)
$56.03M
total volume
254,328,152
settlements
200,040
paying wallets (tracked)
5,034
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,034 distinct pay-to wallets we resolve to a listed endpoint; one seller often runs many endpoints off a single wallet.
Monthly momentum
▼ -9.0% 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) | $946K | 31.9% | 3,420 | 1,020 |
| 2 | api.bitrefill.com | $623K | 21% | 4,857 | 1,529 |
| 3 | 3MZVk9…NfYX (unlisted) | $461K | 15.5% | 1,452 | 389 |
| 4 | FPfGD3…7Vk4 (unlisted) | $205K | 6.9% | 234 | 71 |
| 5 | api.surplusintelligence.ai | $133K | 4.5% | 29,077 | 29 |
| 6 | swarmx.io | $123K | 4.2% | 3,401 | 13 |
| 7 | agentapi.rozo.ai | $54K | 1.8% | 380 | 4 |
| 8 | api.clusterprotocol.ai | $49K | 1.7% | 58,561 | 724 |
| 9 | laso.finance | $36K | 1.2% | 694 | 87 |
| 10 | x402.dtelecom.org | $36K | 1.2% | 16,179 | 30 |
What's broken (402 envelope issues, 30d)
no-envelope7,455,551no-accepts7,211,492missing-x402-version7,133,323http-status-4043,824,337http-status-5023,653,280http-status-5033,159,251http-status-200977,574http-status-400597,121missing-resource-info296,346http-status-410252,876HTTP-native vs MCP-native
reliability split by probe transport
HTTP-nativeplain HTTP 402 paywall
210,968
active endpoints · 99.9%
55.0%
avg uptime (scored)
A · 23,469 B · 65,012 C · 8,705 D · 5,247 F · 74,102 ? · 34,433
MCP-nativex402 challenge served over MCP
230
active endpoints · 0.1%
53.8%
avg uptime (scored)
A · 4 B · 84 C · 39 D · 36 F · 63 ? · 4
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 severalx402scan157,237bazaar60,755thirdweb57,201payai20,571ultravioletadao7,422threews4,960dexter3,254manual569openfacilitator302mcpregistry215anyspend17customer2found 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