How x402 turns a forgotten web status code into payments for AI agents
Coinbase built x402 on HTTP's long-dormant 402 status code, letting AI agents pay for data and services instantly in USDC without accounts or API keys. The x402 Foundation, now managed by the Linux Foundation, counts Visa, Mastercard, Circle, and Stripe among its members.
HTTP status codes are the web's shorthand. Developers know 404 for a missing page and 200 for a successful request. But one code has sat unused for decades: 402, Payment Required. @coinbase has now built an entire payment protocol around it, and the idea is gaining serious momentum.
How the protocol works
The mechanics of x402 are straightforward. When an AI agent requests a resource behind a paywall, the server responds with an HTTP 402 status and machine-readable payment instructions, specifying the price, accepted tokens, and settlement network. The agent signs a stablecoin payment, attaches the proof to a second request, and a third-party facilitator settles the transaction onchain. The server then releases the data. The whole cycle requires no login, no API key, and no human in the loop.
$USDC is the most widely used asset on the protocol, according to Coinbase. The design targets the kind of autonomous, per-request billing that existing rails, built around credit cards and subscriptions, cannot handle cleanly. An AI agent cannot enter card details or negotiate an enterprise contract. x402 is designed specifically for that gap.
An open standard with heavyweight backing
What began as a Coinbase project has become a broad industry effort. The x402 Foundation, managed by the @linuxfoundation, formally launched in July 2026 as the neutral home for the protocol. Founding members span payments, cloud, and crypto, including @circle, @Visa, @Mastercard, Google, Amazon Web Services, Microsoft, Shopify, and Stripe. The foundation maintains shared specifications and coordinates member participation across verticals.
Stripe's presence is notable given that the company also backs a competing standard. The Machine Payments Protocol, developed by Stripe alongside Paradigm, takes a session-based authentication approach rather than x402's per-request model, making the two architecturally distinct. Stripe sitting on both sides of that divide reflects how early and contested this space remains.
The race to build the payment layer for AI-driven commerce is only accelerating. x402 has broad institutional support and a clear technical model. Whether it becomes the dominant standard, or one of several, will depend on how quickly developers and platforms adopt it at scale.
Sources:
Coinbase: Introducing x402, a new standard for internet-native payments
Linux Foundation: Launching the x402 Foundation
CoinDesk: Visa, Stripe and Google join x402 Foundation
Latest News
Read More...
Author
Crypto RichRich has been researching cryptocurrency and blockchain technology for eight years and has served as a senior analyst at BSCN since its founding in 2020. He focuses on fundamental analysis of early-stage crypto projects and tokens and has published in-depth research reports on over 200 emerging protocols. Rich also writes about broader technology and scientific trends and maintains active involvement in the crypto community through X/Twitter Spaces, and leading industry events.













