I've spent the last couple of years going deep on AI — training LLMs, building with coding agents, studying leading tools and architectures. But before that, I spent the better part of a decade in stablecoins and payments infrastructure.
x402 is the first thing I've seen that brings both worlds together in a way that feels inevitable.
The Stablecoin Side
I was at Coinbase when USDC was still early. My team built some of the infrastructure that powered it. Stablecoins were the blockchain use case I was most excited about — a dollar that moves at internet speed, settles in seconds, and works across borders without intermediaries.
That conviction eventually led me to Paxos, where I spent nearly three years building enterprise-grade stablecoin infrastructure. The highlight for me was building and launching PayPal USD end to end and scaling it to a market cap north of $3 billion.
Back in the early days of USDC, one of the use cases people always talked about with stablecoins was machine-to-machine payments. It made sense in theory — programmable money for programmable systems — but it felt a bit sci-fi. There weren't really any machines that needed to pay each other autonomously.
The AI Side
That's changed. In the past two years, AI has gone from "impressive demos" to agents that actually do things. Claude Code writes and ships production software. OpenClaw runs autonomously on a VPS, handling tasks 24/7. Codex takes engineering tickets. These aren't chatbots — they're economic actors that consume APIs, make decisions, and produce real output.
Here's a stat that stuck with me: Mintlify, which powers developer documentation for over 5,000 companies including Coinbase and PayPal, reported that nearly half of all documentation visitors across their platform in December 2025 were AI agents — approaching parity with human traffic. That's not a projection. That's what's already happening in production.
These agents need to access services across the web. And right now, the way we grant access to APIs — manual signup, credit card on file, API key provisioning — was designed for humans. It doesn't scale when the "developer" is an LLM running autonomously.
Enter x402
x402 is an HTTP-native micropayment protocol co-developed by Coinbase and the Cloudflare Foundation. It revives the HTTP 402 "Payment Required" status code — which has been reserved but unused since the early days of HTTP — and turns it into a real payment flow.
The mechanics are straightforward: an agent requests a resource, the server responds with a 402 status and a price, the agent signs a stablecoin payment, and the server delivers the resource. No API key. No subscription. No account. Just pay and use.
The protocol has been live since May 2025 and has already seen significant activity — millions of transactions per month across over a thousand independent projects, with three quarters of services priced between one and ten cents. To be fair, a lot of the early volume has been driven by crypto-native use cases like memecoin launches rather than the kind of durable API commerce I find most interesting. But the protocol works, the rails are live, and the use cases are starting to diversify. That matters more than the headline numbers right now.
Why This Fits
The more I dig into x402, the more I think stablecoins and AI agents are a natural fit for each other — specifically for API access. A few reasons:
No API keys needed. When a wallet is your identity, authentication and payment happen in the same step. An agent doesn't need to sign up, wait for approval, or manage rotating keys. It just pays and gets access. This is a big deal when you have thousands of agents that each need to access dozens of services.
True pay-per-use. Traditional API pricing forces you into monthly plans or prepaid credits. Agents don't work that way — they might hit an API once or a thousand times in a day. x402 lets them pay per request, exactly matching cost to consumption.
Micropayments that actually work. This is where the stablecoin piece really matters. Try charging one cent on a credit card — the fee floor alone is around 30 cents per transaction, plus a percentage. A one-cent API call on card rails would incur 3,000% overhead in fees. On stablecoin rails, the transaction cost is a fraction of a cent, and settlement happens in under a second rather than two business days.
No human in the loop. Card payments require a cardholder — someone with a name, an address, a credit history. Agents don't have any of that. Stablecoins don't care. A wallet address is sufficient identity for a payment, and the payment itself is the authorization.
To put it concretely: imagine an API provider processing 10,000 agent requests at a fraction of a cent each. On card rails, the minimum fees alone would exceed the total revenue. On x402, the provider keeps virtually all of it.
What's Still Missing
I don't want to oversell the current state. There are real challenges.
Standards are still evolving. x402 V2 launched in December 2025 with multi-chain support and a plugin architecture, but the ecosystem is still young. Tooling, client libraries, and facilitator options are improving quickly but aren't mature yet.
The trust layer doesn't exist yet. Payments are only one piece of a functioning commerce system. Who is this agent? Is this payment compliant? Do the API logs match the payment records? Traditional payment networks spent decades building the infrastructure surrounding the transaction — fraud detection, dispute resolution, compliance screening, reconciliation. Stablecoin rails need equivalent infrastructure, and most of it hasn't been built yet.
Adoption is bootstrapping. The protocol needs both buyers (agents) and sellers (API providers) to show up. That classic chicken-and-egg dynamic is playing out now. The numbers are encouraging, but this is still early.
These aren't dealbreakers — they're the kind of problems that get solved when a market is forming. And things are moving quickly. Google's AP2 protocol integrated x402 for stablecoin settlement. The stablecoin market itself has grown from under a billion dollars in 2019 to over $300 billion today. Visa is settling billions in stablecoins annually. The infrastructure layer is maturing fast.
Looking Ahead
What excites me about x402 is that it's not trying to replace existing payment systems. It's enabling a category of transactions that simply couldn't happen before — sub-dollar, high-frequency, machine-to-machine payments across the open web, with instant settlement and near-zero fees.
To get a feel for what this looks like in practice, I built TinyBrain — a small AI agent that earns USDC by charging a penny per query via x402, and spends it to pay smarter models for help on harder questions. No API keys, no user accounts, no subscriptions. Just a wallet and a protocol. It's a toy, but it demonstrates the full loop: an autonomous agent earning and spending money on the open web.
The convergence of capable AI agents and programmable money feels like one of those moments where two independent technology curves cross and something new emerges. I've been on both sides of that equation, and I'm paying close attention to what's being built at the intersection.
If you're thinking about this space or building in it, I'd love to connect — feel free to reach out.