Coinbase CEO Brian Armstrong posted something short and blunt on X this month:
"x402 is inevitable. Every agent is going to need to pay for things. And there will be far more agents than humans."
It's the kind of line that reads like a founder talking his own book — Coinbase did, after all, create x402. But strip away the bravado and there's a real thesis underneath it: agents are a fundamentally different kind of economic actor, and the rails built for humans — bank accounts, card networks, three-day wires — don't work for something that might spin up, transact, and shut down in the same minute. Armstrong's bet is that stablecoin-native, HTTP-embedded payments are what fills that gap. The interesting part isn't whether he's right in theory. It's how much of that future has already started showing up in the data.
Coinbase built it, but Coinbase doesn't run it anymore
x402 started as a Coinbase project — a way to resurrect the long-dormant HTTP 402 "Payment Required" status code and turn it into a real payment rail for machines. But by design, Coinbase handed the keys over. The protocol's governance now sits with the x402 Foundation, an independent body under the Linux Foundation, with dozens of members spanning payments, cloud, and crypto — a deliberate move to make x402 a neutral standard rather than a Coinbase product.
That's part of why the growth numbers are worth taking seriously instead of dismissing as a CEO hyping his own protocol. By Coinbase's own count, x402 has processed well over 169 million payments across roughly 590,000 buyers and 100,000 sellers in its first year — a scale that's hard to write off as a demo. And the infrastructure keeps expanding underneath it: AWS added native x402 support to CloudFront, Cloudflare is running its own facilitator and a waitlisted Monetization Gateway, and Google built x402 directly into the stablecoin rail of its Agent Payments Protocol (AP2). None of that required Coinbase's permission or involvement — which is exactly the point of handing the standard to a foundation.
The part Armstrong's post doesn't say out loud
Here's what gets lost in a single tweet: x402 was never a Base-only or even a Coinbase-only story, and it isn't becoming one. Solana has been one of the earliest and heaviest users of the protocol — by Solana's own figures, it's driven the majority of x402 transaction volume this year — and that activity hasn't slowed down. AI agents moved roughly 3.3 million USDC through x402 on Solana in a single week this month alone. Multi-network settlement isn't a footnote to the x402 story anymore; for a meaningful share of real transaction volume, it's the main story.
That's the gap a multi-network facilitator is built to close — routing x402 payments across Base, Solana, and whatever settlement layer comes next, instead of betting merchants and agents on a single chain. Armstrong is right that agents will need to pay for things. He's just not the only one building the rails for how.
Why this matters beyond the crypto headlines
The signal worth watching isn't Armstrong's tweet — it's who's showing up around it. Accounting standards are catching up (FASB has proposed letting stablecoins count as cash equivalents on the balance sheet), cloud providers are shipping native support, and Google is routing agent-to-agent payments through the same protocol. That's the pattern of a standard maturing past its founder, not a company running a marketing campaign.
For builders, the practical takeaway is simple: x402 is no longer a bet on one company or one chain. If you're building on the protocol, the question isn't whether to support it — it's whether your integration can handle a genuinely multi-network world instead of assuming Base is the only settlement layer that matters.
Want to see it in practice? The x402 quickstart walks through accepting your first agent payment in a few minutes, and the PayAI GitHub has reference implementations for both Solana and Base settlement.