HTTP status code 402 was reserved in the original HTTP spec back in 1997. The description read “Payment Required.” For nearly three decades, nobody used it. In early 2026, Coinbase shipped x402, an open protocol that finally gives that status code a job. Now AI agents can pay for API calls with stablecoins, automatically, in a single HTTP round-trip. No accounts, no API keys, no invoices.

As of May 2026, x402 is not theoretical. It is running in production, processing real transactions, and showing up in MCP server configurations. Here is what is actually happening.

What x402 Does

The protocol is simple. A client makes an HTTP request to an API or MCP server. The server responds with 402 Payment Required and includes a payment envelope: the blockchain network (usually Base or Solana), the token contract (typically USDC), the amount, and the recipient address. The client signs a transfer authorization, retries the request with a PAYMENT-SIGNATURE header, and the server verifies and settles onchain before returning the response.

No session tokens. No OAuth flows. No billing portals. The entire payment happens inline with the API call.

This matters for AI agents because they do not have credit cards. An agent running autonomously needs a way to pay for services programmatically. x402 gives it exactly that: a wallet, a signature, and a stablecoin transfer that settles in seconds.

The Numbers So Far

Coinbase disclosed 165 million x402 transactions across 69,000 active agents as of April 2026. On Solana alone, the protocol has processed over 35 million transactions and more than $10 million in volume since launch. These are not test transactions on a devnet. This is real money moving between real services.

The adoption curve accelerated fast. Stripe added x402 support in February 2026. Cloudflare’s Agents SDK ships with a reference implementation. AWS launched Amazon Bedrock AgentCore Payments in preview in May 2026, giving agents built on Bedrock native x402 micropayment capabilities with wallet management, spending policies, and audit trails baked in.

x402-Enabled Servers in the Directory

The AgentNDX directory tracks 276 MCP servers across 10 categories. The payments category includes 14 servers, and x402 support is starting to appear across them.

Servers with x402 enabled today:

  • agentndx (data): The AgentNDX registry itself accepts x402 payments at $0.005 per query. Install via https://agentndx.ai/mcp.
  • bedrock-agentcore-payments (payments): AWS managed payment infrastructure for Bedrock agents, with native x402 support, IAM guardrails, and CloudTrail logging.

Payment-focused MCP servers that can facilitate or process x402 transactions:

  • stripe-agent-toolkit (payments): Stripe’s official MCP server. Since Stripe added x402 support in February, agents can process stablecoin payments alongside traditional card payments.
  • coinbase-agentkit-mcp (payments): Coinbase’s AgentKit, the team that built x402. This server provides wallet creation, token transfers, and direct x402 payment handling.
  • paypal-mcp (payments): PayPal’s MCP server for payment processing and merchant tools.
  • plaid-mcp (payments): Financial data access and account linking for agents that need to verify balances or fund wallets.

How to Add x402 to Your Own MCP Server

The pattern is straightforward. When your server receives a tool call, check whether the caller has included a valid payment signature. If not, return a 402 response with the payment details. If the signature is valid, verify it onchain, then execute the tool and return results.

Coinbase publishes a reference implementation, and Zuplo has documented the full middleware pattern for gating MCP tool calls with x402. The typical flow:

  1. Client calls tools/call on your MCP server
  2. Server responds with 402 and a payment envelope (chain, asset, amount, recipient)
  3. Client signs an EIP-3009 transferWithAuthorization payload
  4. Client retries with the PAYMENT-SIGNATURE header
  5. Server verifies, submits onchain, and returns the tool result

Most implementations use USDC on Base for low fees and fast finality. Settlement typically confirms in under two seconds.

x402 vs. Stripe MPP

Developers building paid MCP servers face a choice: x402 or Stripe’s Metered Payment Protocol (MPP). The short version:

x402 works best for micropayments (fractions of a cent to a few dollars), cross-border transactions, and fully autonomous agents. No accounts needed. Settlement is onchain and near-instant. The tradeoff is that your users need a crypto wallet.

Stripe MPP works best if your users already have Stripe accounts, you want traditional currency settlement, or you need established dispute resolution. The tradeoff is higher per-transaction overhead and the requirement for account setup.

Many teams are supporting both. The protocols are not mutually exclusive.

What This Means for the Ecosystem

x402 solves a real problem that was blocking the agentic economy. Before it existed, every paid API required bespoke authentication, billing accounts, and human intervention to set up. That does not work when you have thousands of agents making millions of micro-transactions per day.

The first wave is already live. The second wave, where most commercial MCP servers accept x402 by default, is forming now. AWS backing it with AgentCore Payments is a strong signal that this is not a crypto-only niche. It is becoming standard infrastructure.

If you are building an MCP server and plan to charge for it, x402 should be on your roadmap. The protocol is open, the tooling is mature, and the transaction volume proves the demand is real.

FAQ

Is x402 only for crypto-native developers? No. The protocol uses stablecoins (primarily USDC), which are pegged to the US dollar. You do not need to understand DeFi or hold volatile crypto assets. Coinbase AgentKit and AWS AgentCore Payments both abstract away most of the blockchain complexity.

Which networks does x402 support? Base and Solana are the most widely used due to low fees and fast finality. Stellar also has x402 support. More networks are expected to follow.

How much does a typical x402 transaction cost in gas fees? On Base, gas fees for a USDC transfer are typically under $0.01. On Solana, they are fractions of a cent. This makes micropayments viable in a way that was not possible on Ethereum mainnet.

Can I use x402 with Claude Desktop or Cursor? Yes, if the MCP client supports x402 payment flows. Wallet management can be handled through Coinbase AgentKit or a local wallet configuration. Check your client’s documentation for x402 support status.

Where can I find x402-enabled MCP servers? The AgentNDX directory tracks x402 support as a protocol filter. You can search for servers with x402 enabled and see pricing per call.