What x402 is
x402 revives the dormant HTTP 402 Payment Required status code as a standard way for software — increasingly AI agents — to pay for APIs, data, and services in stablecoins (mostly USDC on Base). A client hits an endpoint, gets a 402 with payment instructions, pays on-chain, and retries with proof. No accounts, no API keys, no invoices.
Why the number is contested
Because x402 settles peer-to-peer on public chains, anyone can measure it — and everyone measures it differently. Raw explorers sum every transfer, which sweeps in three kinds of non-revenue: wash trading (wallets paying themselves to inflate rank), dust (sub-cent spam loops), and facilitator settlement(aggregators routing other people’s payments through their own wallet, which then looks like the #1 “seller”). Filter those out and the market is roughly half the size of the headline.
The honest figure
x402stats publishes both: the raw total (comparable with explorers) and the organic total (wallets with ≥ $100 revenue, ≥ 3 distinct buyers, average payment ≥ $0.001, excluding known settlement wallets). The gap between them is the story. See the current figures on the live dashboard, the reasoning on the methodology page, and the monthly write-up in State of x402.
Is x402 growing?
Adoption is early and volatile. Reported volume spiked during a late-2025 artificial-volume wave (a single day topped $3M) and has since normalized to a smaller, more organic base. The metric that matters isn’t peak volume — it’s the count of businesses that actually earn, which we track every month.