An API that charges for queries has always been awkward. Subscription tiers and monthly billing break down when autonomous agents make thousands of microtransactions per hour across new services. x402 is Coinbase’s bet that the missing piece is a payment primitive wired directly into HTTP.

The mechanism revives HTTP status code 402 “Payment Required.” When a client requests a resource, the server responds with 402 plus machine-readable payment terms: amount, asset, network, and recipient.

The client pays in USDC and retries with a cryptographic payment proof in an HTTP header. The server verifies settlement on-chain and serves the resource.

Coinbase released x402 in May 2025. By December, it had processed 75 million transactions worth $24 million for paid APIs and AI agents. V2 adds modularity: network-agnostic identifiers, pluggable facilitators, wallet hooks, and a “Bazaar” discovery layer.

Cloudflare announced it will integrate x402 and co-launch the x402 Foundation. Google Cloud’s Agent Payments Protocol uses x402 for on-chain settlement. CryptoSlate will integrate it soon. Solana and Base are the production networks, with Solana reportedly flipping Base in volume by late 2025.

Facilitators as payment gateways

The complexity lies in the “facilitator,” which monitors blockchain networks, verifies payments, generates signed authorizations, and exposes an HTTP interface so websites can avoid running nodes.

Coinbase’s hosted facilitator offers fee-free USDC payments on Base and Solana with high-throughput settlement. The protocol supports multiple independent operators, but whether that portability survives when Coinbase’s facilitator is free and deeply integrated is an open question.

Refunds work differently from card networks. x402 has no network-level reversal. Merchants send a compensating transfer and update the order state. Rate limiting is an application-layer feature: the 402 response encodes metering rules, and facilitators enforce per-wallet limits.

That makes x402 closer to cash than reversible card payments, a feature for high-frequency API calls where chargebacks would be ruinous, but a liability for consumer flows that need buyer protection.

Ecosystem gravity

Cloudflare’s alignment signals x402 is infrastructure, not just a Coinbase project.

Integrating x402 into Cloudflare’s edge compute and CDN stack enables payment requests to fit into everyday web workflows. The Foundation framing of open governance and multiple implementers positions the protocol as shared plumbing.

Google Cloud’s AP2 uses x402 for agent-to-agent settlement, tying it into hyperscaler AI stacks. Wallets like OneKey, Sahara, and Transak have integrated x402 as a default primitive.

Case studies mention AEON settling AI-initiated payments to millions of merchants across Southeast Asia, Latin America, and Africa.

Throughput is small, just $24 million over seven months, but the trajectory matters. If autonomous agents need to pay per call rather than per month, x402 becomes necessary plumbing. The bet is that embedding payments in HTTP reduces friction enough to unlock new transaction classes.

Risks and control

The most considerable risk is that Coinbase’s CDP service is the most mature.

Cloudflare and AP2 reduce protocol-level concentration, but early traffic flows through Coinbase infrastructure. Coinbase shapes adoption by deciding which chains to prioritize and how aggressively to subsidize fees.

The facilitator is free today, but that rarely lasts once network effects lock in.

Compliance is baked into facilitators. x402 itself is neutral, but hosted facilitators plug into KYT and sanctions screening, and political pressure concentrates on facilitator operators.

Token confusion is endemic, as exchanges list speculative tokens branded “x402,” conflating the protocol with unrelated assets. The team stresses the protocol has no native token, but that message competes with listing announcements.

For Solana and Base, x402 is a bet that high-throughput, low-cost chains win the agent economy. If the modal payment is $0.01 for an API call, Ethereum mainnet is out, and L2s with multi-cent fees struggle.

Solana’s flip of Base in volume suggests faster finality and lower gas costs, giving it a structural advantage when agents hammer APIs thousands of times per second.

The constraint is that x402 solves coordination, not liquidity. An agent paying for an API call needs USDC in a hot wallet: custodying keys, managing balances, handling risk.

For developers, it is manageable, but for enterprises deploying agent fleets, it becomes a compliance nightmare. The protocol makes payments manageable, but it does not ensure the surrounding infrastructure is safe.

x402 is not the first attempt to wire payments into HTTP. What is different is the combination of stablecoins, cheap blockchains, and a credible use case in autonomous agents.

Whether that overcomes coordination problems and regulatory friction will determine whether x402 becomes foundational plumbing or another experiment that never escapes the lab.

The post What is x402? The HTTP-402 payments standard powering AI agents, explained appeared first on CryptoSlate.