The x402 protocol is an open payment standard that uses HTTP 402 status code to enable AI agents to make instant stablecoin payments onchain, turning any API endpoint into a paywall that machines can navigate without human intervention, credit cards, or subscription accounts. Developed by Coinbase and backed by the x402 Foundation, the protocol solves a fundamental problem: autonomous software cannot sign up for SaaS accounts, enter credit card details, or negotiate enterprise contracts the way humans do.

What Problem Does x402 Actually Solve?

For decades, HTTP 402 Payment Required has sat unused in the web's technical specification since the early 1990s. Credit cards, OAuth tokens, and API keys filled the gap instead, but these mechanisms break down when the buyer is not a human but an autonomous AI agent. The x402 protocol revives that forgotten status code and pairs it with stablecoin payments to create a payment method native to the web's request-response model.

When an AI agent requests a resource that costs money, the server replies with an HTTP 402 response that includes payment instructions. The agent reads those instructions, signs a stablecoin transaction, attaches the proof, and retries the request. The server verifies the payment and returns the data. The entire cycle takes seconds, requires no login, and settles onchain.

How Does the x402 Payment Flow Actually Work?

The x402 payment system operates through a simple request-response cycle between three parties: the client (the AI agent making the request), the resource server (the API requiring payment), and the facilitator (an onchain verification and settlement service). Understanding this flow reveals why the protocol is designed to work without human intermediaries.

• Request Phase: The client sends a standard HTTP request to the resource server for a resource or service.
• Payment Instructions: If payment is required, the server responds with HTTP 402 and includes payment instructions in a structured header, specifying the price, accepted tokens, recipient address, and settlement network.
• Payment Construction: The client reads the payment instructions and constructs a signed payment payload using either EIP-3009 tokens like USDC for gasless authorization or Permit2 for other ERC-20 tokens.
• Retry with Proof: The client retries the original request with the signed payment attached in a header.
• Verification and Settlement: The resource server forwards the payment to a facilitator, which verifies the signature, checks the client's balance, and settles the payment onchain before the server delivers the requested resource.

The facilitator is a critical piece of this architecture. It abstracts away onchain complexity so that resource servers do not need to run blockchain nodes or manage wallets themselves. Coinbase and other providers operate public facilitators that handle verification and settlement for free on supported networks.

Which Blockchains and Tokens Does x402 Support?

The x402 protocol is chain-agnostic by design. Its payment header format does not assume a specific blockchain; instead, it describes the network, token, amount, and recipient, leaving settlement to the facilitator. As of early 2026, x402 is live on multiple networks with varying finality times and token support.

Base and Solana are the most commonly used networks for x402 payments due to low fees and fast finality. Base transactions settle in approximately two seconds, while Solana settles in roughly 400 milliseconds through Coinbase's facilitator. Stellar transactions settle in about five seconds, Arbitrum in roughly one second, Polygon in approximately two seconds, and Ethereum Layer 1 in about 12 seconds. Most x402 transactions settle in stablecoins, primarily USDC, which is the dominant settlement token across the protocol.

The protocol supports USDC and EURC natively via EIP-3009 for gasless transfers, and it works with any ERC-20 token through Permit2. Public facilitators from Coinbase via Coinbase Developer Platform (CDP) are available for Base, Solana, and Stellar at no cost. Third-party facilitators can also be deployed for custom settlement logic, alternative chains, or specialized compliance requirements.

Who Is Building the x402 Ecosystem?

Coinbase and Cloudflare launched the x402 Foundation in 2025 to establish x402 as the universal standard for internet-native payments. Foundation membership has expanded rapidly to include Google, Visa, AWS, Circle, Anthropic, and Vercel alongside the founding partners. The breadth of this coalition, spanning cloud infrastructure, payments, AI, and cryptocurrency, signals that x402 is being positioned as foundational infrastructure for the agentic economy rather than a crypto-only standard.

The ecosystem spans several categories of builders and integrations. Infrastructure providers like Cloudflare have integrated x402 into their Workers platform and are piloting a pay-per-crawl product. Vercel supports x402 middleware for serverless functions, and Zuplo offers x402 paywalls for API gateway customers. AI agent frameworks are adding x402 support so that AI models can pay for tool calls and data access autonomously through Model Context Protocol (MCP) servers.

Identity and verification providers like World (formerly Worldcoin) have integrated agent-identity tooling with x402, attaching cryptographic proof of human identity to AI agent transactions for stablecoin micropayments. Payment aggregators such as Kobaru provide a transparent proxy layer that lets vendors add x402 paywalls to existing APIs without modifying backend code, while Agently operates a routing and settlement layer for agent-to-agent commerce.

Financial institutions are also joining the ecosystem. Visa added x402 support through its Trusted Agent Protocol (TAP), and Stripe integrated x402 through its Agent Commerce Protocol (ACP), connecting the protocol to traditional payment rails. On Solana, the protocol has seen meaningful adoption since the chain integration shipped in mid-2025, and across all networks, adoption is accelerating as more APIs add x402 paywalls and more AI agents gain wallet capabilities.

How to Implement x402 for Your API or Service

• Choose Your Facilitator: Select a public facilitator like Coinbase CDP for Base, Solana, or Stellar, or deploy a third-party facilitator for custom settlement logic or alternative blockchains.
• Select Your Settlement Network: Decide which blockchain best fits your use case based on finality time and transaction costs; Base and Solana offer the fastest and cheapest options.
• Configure Payment Instructions: Set up your API to respond with HTTP 402 and include payment instructions in the response header, specifying the price, accepted tokens, recipient address, and settlement network.
• Integrate with Existing Infrastructure: Use proxy layers like Kobaru to add x402 paywalls to existing APIs without modifying backend code, or integrate x402 middleware directly into your serverless functions if using Vercel.
• Test with AI Agents: Build or test with x402-enabled MCP servers so that AI models can autonomously pay for your resources and verify the payment flow works end-to-end.

The x402 protocol represents a shift in how machines interact with paid services on the internet. By embedding stablecoin payments directly into HTTP, it removes friction that has traditionally required human oversight, subscription management, and pre-existing relationships between buyer and seller. As more infrastructure providers, AI frameworks, and financial institutions adopt the standard, the protocol is poised to become the default payment mechanism for autonomous software in the coming years.