x402 is an open payment standard developed by Coinbase that revives the web's long-unused HTTP 402 status code, allowing AI agents and applications to pay for online services. Payments are made primarily in USDC on Base and settled through facilitators, meaning buyers sign a payment authorization instead of creating accounts or API keys. More than 50 companies, including Visa, Mastercard, and Google, have joined the x402 Foundation, which now governs the protocol under the Linux Foundation.

The web was never built with payments in mind. Early HTTP specifications included a status code, 402 "Payment Required," that was reserved for a future system of online payments, and it then sat unused for roughly 30 years. Traditional digital payments were slow and expensive, requiring accounts, card details, and middlemen capable of reversing charges—none of which suits a small payment made by software.

That gap matters more now because AI agents are starting to browse, call APIs, and buy services on their users' behalf. An agent cannot fill in a checkout form or sign up for a monthly plan for every tool it uses. Cloudflare says more than half of internet traffic is now non-human, and it reports seeing one billion HTTP 402 responses on its network every day. x402 is an attempt to finally give the internet a native way to pay. This guide covers what it is, how it works, who backs it, and whether a token is involved.

The 402 "Payment Required" code has been part of the HTTP standard since the 1990s. Status codes are how web servers signal the outcome of a request—the same family as the familiar 404 "Not Found"—and 402 was set aside "for future use," making x402 the first major effort to actually put it to work.

What Is x402?

x402 is an open payment standard built on top of HTTP, the protocol that moves data around the web. Coinbase launched it in May 2025 with partners including AWS, Anthropic, Circle, and NEAR. It lets APIs, apps, and AI agents pay for services in stablecoins as part of an ordinary web request.

x402 is neither a blockchain nor a coin. It is a set of rules—message formats, headers, and a request-and-response flow—that any server or client can follow. Payments are made mostly in USDC, Circle's dollar-backed stablecoin, with Coinbase's Ethereum layer-2 network Base serving as the main settlement chain. Layer-2 networks process transactions away from Ethereum's main chain and settle the results back to it, which is what lets Base clear x402 payments in seconds at sub-cent cost. The protocol works with any chain, however, and now supports Solana, Polygon, Arbitrum, and others, as well as traditional card payments.

On April 2, 2026, the Linux Foundation announced the launch of the x402 Foundation, with Coinbase contributing the protocol and companies including Microsoft, Google, Visa, and Mastercard expressing initial support. The new foundation became fully operational on July 14, 2026, and now stewards the protocol under vendor-neutral governance—the same stewardship model the Linux Foundation applies to the Linux operating system and other open projects.

We are excited to introduce x402–a new open source payments protocol built on HTTP rails. Let's break it down: pic.twitter.com/9PNI49NK7A — Coinbase Developer Platform🛡️ (@CoinbaseDev) May 6, 2025

How Does x402 Work?

x402 operates through a short handshake inside a normal web request:

1. Request: An AI agent or app asks a server for something, such as an API call, a dataset, or an article.
2. 402 response: The server replies with "402 Payment Required" and includes machine-readable terms: the price, which tokens it accepts, and the wallet address to pay.
3. Payment: The client signs a payment authorization with its wallet and sends the request again with that signature attached in a header.
4. Delivery: The server checks the payment, settles it onchain, and returns what was asked for.

Most of the onchain work is handled by a facilitator, a service that verifies payments and settles them on the blockchain so sellers do not have to run their own crypto setup. On EVM chains, x402 uses EIP-3009, a standard that lets someone transfer tokens by signing a permission instead of sending a transaction themselves. This means the buyer does not need to hold ETH for gas.

What Makes x402 Different?

x402's core proposition is very small payments made by machines. Settlement on Base takes seconds and costs well under a cent, so it is practical to pay fractions of a cent for a single API call. There is no sign-up, no API key, and no subscription—the agent simply pays and receives what it requested.

Adoption has grown quickly. Coinbase released x402 V2 in December 2025, which added wallet-based identity so agents do not have to pay again on every call, along with automatic service discovery and support for more chains. In May 2026, it added batch settlement, in which agents hand sellers signed vouchers that can be settled in bulk.

x402 had processed more than 196 million transactions across 12 chains as of November 1, 2026, settling more than $42 million in total, according to Fireblocks, which cited data from tracker agenteconomy.to—an average of roughly 21 cents per transaction. Coinbase says more than 97% of onchain agent transactions in Q2 2026 used x402.

It is worth noting, however, that more than half of x402's lifetime transactions came from a two-month frenzy in late 2025, when traders ran automated scripts to mint and sell PING, a token issued through x402, according to Fireblocks. Activity has since settled at a much lower level: in October 2026, x402 processed 5.1 million transactions worth about $274,000.

Who Is Working With x402?

• Cloudflare: Co-developer of the x402 Foundation with Coinbase and Stripe, with x402 support in its Agents SDK and a monetization gateway that runs at the network edge.
• Stripe: Co-developer of the x402 Foundation and a premier member that turns x402 payments into its standard PaymentIntents, so merchants can receive familiar reporting and payouts in regular currency.
• Agentic.Market: Coinbase's public marketplace, launched in April 2026, for discovering and comparing x402 services, with live pricing and volume data.
• CoinGecko: Offers crypto market data API endpoints that agents pay for per call.
• AWS: Its AgentCore service manages agent payments, budgets, and permissions on the buyer side.
• Google: Its agent-to-agent (A2A) x402 extension, part of its Agent Payments Protocol (AP2) and built with Coinbase, the Ethereum Foundation, and MetaMask, uses x402 for crypto settlement between agents.

Does x402 Have a Token?

No. x402 is a protocol, not a cryptocurrency, and it has no official native token. Payments are made in existing stablecoins, mostly USDC. Speculative "x402" tokens have appeared on various chains, but none of them is issued or backed by Coinbase or the x402 Foundation. Readers should be wary of any token claiming to be the official x402 coin.

Where to Get USDC for x402 Payments

To use x402, an agent or app needs a wallet holding a supported stablecoin on a supported network—usually USDC on Base. USDC is widely available on major exchanges including Coinbase, Kraken, and Binance, and Coinbase lets users send USDC straight to Base. Developers can also use Coinbase Developer Platform wallets or Circle Wallets to fund their agents, and can set spending limits to keep those agents under control.

The Road Ahead

The x402 Foundation is growing fast. It had 40 member organizations when it became operational in July 2026, and its member list has since grown to 57, including Visa, Mastercard, American Express, PayPal, Google, Shopify, Circle, Stripe, and AWS. Michael Hursta became the foundation's executive director on October 1, 2026.

x402 is not the only option, however. The Agentic Commerce Protocol, an open standard developed by Stripe and OpenAI, and Visa's Trusted Agent Protocol are competing for a role in agent payments, even though Stripe and Visa are also premier members of the x402 Foundation. Stripe has additionally co-developed the Machine Payments Protocol with payments blockchain Tempo. Like x402, MPP uses the HTTP 402 code to let agents pay for services, but adds session-based billing so agents can pay as they go rather than settling every request onchain. Since June 2026, it has also supported x402 payments.

The big open question is whether x402's large transaction counts turn into steady, real commerce. If they do, the payment code that sat unused for 30 years could end up carrying much of the AI economy's payments.