x402: Open Micropayments for AI Agents

While ACP and UCP open up traditional e-commerce for AI agents, x402 and related protocols pursue a more radical vision: an open, permissionless payment system embedded directly in HTTP — without platforms, without gatekeepers, without minimum amounts.

HTTP 402: A 28-Year-Old Code Becomes Relevant

When Tim Berners-Lee and the HTTP standardization team defined the HTTP status codes in 1997, they reserved code 402 — "Payment Required". The idea: web servers could directly require payment before delivering content. But there was no functioning micropayment system, so 402 remained unused for nearly three decades.

Now, with stablecoins, on-chain payments, and AI agents capable of automated transactions, the code becomes practically relevant for the first time. x402 uses it exactly as originally intended: a server responds with 402, the agent pays automatically, the server delivers the content.

The a16z Vision: Open Agentic Commerce

In March 2026, a16z Crypto (Andreessen Horowitz) published a manifesto for "Open Agentic Commerce." The core thesis:

a16z argues: Agentic Commerce needs its own open infrastructure — protocols that no company controls, that require no permission, and that anyone can implement.

x402 by Coinbase

x402 is the concrete implementation of this vision, developed by Coinbase. The principle is elegantly simple:

1. An AI agent calls an API or web resource
2. The server responds with HTTP 402 and a payment header (price, wallet address, accepted tokens)
3. The agent executes an on-chain payment in USDC (stablecoin)
4. The agent sends the payment proof in the next request
5. The server verifies the payment and delivers the content

Why stablecoins? Credit cards have minimum transaction fees of about 30 cents — for an API call costing $0.001, that is untenable. Stablecoin transactions on Layer 2 networks cost fractions of a cent. This solves the micropayment problem that has remained unsolved since the 1990s.

mpp by Tempo and Stripe

The Micropayment Protocol (mpp) by Tempo takes a similar approach but with broader payment support. Stripe is involved as a partner, bridging the stablecoin world and the traditional payment system.

While x402 relies purely on stablecoins, mpp could also support traditional payment methods — important for providers who do not want to build crypto infrastructure.

AgentCash: One Balance for Everything

The "AgentCash" concept describes a world where an AI agent has a single balance — funded by the user — and can use it to pay for any API, any service, and any product on the internet. No separate accounts, no API keys, no billing contracts.

An agent with AgentCash could:

• Pay for premium data sources (weather data, financial information)
• Use AI services from other providers (image generation, translation)
• Unlock digital content (articles, reports, analyses)
• Pay for API calls to third-party providers

Permissionless Commerce

The most important conceptual difference from ACP and UCP: x402 is permissionless.

With ACP, a merchant must register, integrate Stripe, and be approved by OpenAI. With UCP, a merchant must be Google-compatible. This creates gatekeepers.

With x402, a provider only needs: a web server, a wallet address, and the ability to set a 402 header. No business development, no whitelist, no platform approval. Anyone can participate.

Critical Assessment

• Very early: x402 and mpp are at a significantly earlier stage than ACP or UCP. There is no mass adoption yet.
• Crypto dependency: Using stablecoins requires crypto infrastructure — wallets, on-ramps, network understanding. For many users and merchants, this is a hurdle.
• Regulatory uncertainty: Stablecoin regulation varies significantly between countries. In the EU, MiCA rules apply, which entail compliance efforts.
• Not an e-commerce standard: x402 solves micropayments but not a complete purchase process. For carts, shipping addresses, and returns, ACP or UCP is still needed.
• Network effects: Closed platforms like ChatGPT have hundreds of millions of users. Open protocols must first achieve this critical mass.

Nonetheless: the vision of an open, permissionless commerce infrastructure for AI agents is compelling in the long term. If the history of the internet is any indicator, open standards will complement closed platforms — and in many areas, replace them.