x402 Protocol: The Payment Layer AI Agents Needed

Martin Kelly is the founder of Botonomy, where he spends his days wiring up AI agents to pay for things on the internet — one HTTP 402 response at a time.

What Is the x402 Protocol?

The x402 protocol is an open payment standard that uses the HTTP 402 status code to let AI agents pay per API call with stablecoins. It requires no accounts, no API keys, and no subscriptions. The agent sends payment proof inside the HTTP request itself, the server verifies and settles the payment, and the resource is returned. It takes two requests: the first gets the 402 with the payment terms, the paid retry gets the result.

HTTP status code 402 has been “reserved for future use” since January 1997, when RFC 2068 first defined it. Nearly three decades later, RFC 9110 still carries the same reservation. x402 finally activates that dormant status code and gives it a production-grade purpose: machine-to-machine payments at the protocol layer.

The protocol is blockchain-agnostic. It supports all EVM-compatible chains, Solana and more, with stablecoin payments as the primary settlement method. This is not a single-chain experiment. It is a multi-chain payment layer designed for the open internet.

Adoption numbers need care. The x402.org dashboard shows 75.41 million transactions and $24.24 million in volume under a “Last 30 Days” label, but Solana Compass reported the same four figures for the 30 days ending 24 August 2026, and they were unchanged on 14 September. Treat that counter as a snapshot, not a live measure. One clarification: x402 is a payment protocol, not a cryptocurrency. It moves existing stablecoins between buyers and sellers. The standard itself is not something you buy, in the same way you do not buy HTTP.

How Does the x402 Protocol Work Step by Step?

The basic x402 payment follows four steps.

Step 1: The client requests a resource. An AI agent sends a standard HTTP request to a server endpoint — exactly the way any API call works today.

Step 2: The server responds with HTTP 402. Instead of returning data, the server sends back a 402 Payment Required status code. The response includes a structured header specifying the payment amount, accepted stablecoins, supported chains, and a payment destination address.

Step 3: The client signs a payment and retries. The agent reads the payment requirements, constructs a stablecoin transaction, cryptographically signs it, and resends the original request with payment proof attached in the headers.

Step 4: The server verifies, settles, and returns the resource. The server validates the payment proof, settles the transaction on-chain, and delivers the requested data. Two requests, one payment.

This matters for AI agents because it removes the steps built for humans that stop autonomous software from using paid services. No sign-up forms. No stored credit cards. No OAuth flows. No API-key provisioning. The payment is the authentication.

The protocol itself is free for both buyer and seller. x402.org describes the cost as “nominal payment network fees”. The x402 GitHub repository and Coinbase’s developer documentation serve as the canonical implementation references for anyone building a client or server.

Who Created x402 and Who Backs It?

x402 was incubated by the Coinbase Developer Platform team, according to Solana’s x402 page. x402.org describes it as “an open, neutral standard for internet-native payments”.

On 23 September 2025, Cloudflare announced it was partnering with Coinbase to create the x402 Foundation. Cloudflare also added x402 support to its Agents SDK and MCP servers: agents built with the SDK can pay for resources, and MCP servers can expose tools that are paid for via x402.

Coinbase hosts developer documentation and operates the x402 Bazaar, a discovery catalog for x402-enabled services. The standard is blockchain-agnostic, and Solana publishes its own x402 developer page alongside the EVM ecosystem.

Why AI Agents Need Pay-Per-Call Payments

Autonomous agents hit a wall the moment they encounter a paywall. Sign-up forms require human input. Credit card fields need PCI-compliant storage. OAuth flows demand browser redirects. Subscription commitments assume predictable, recurring usage.

An agent can be scripted to click through a sign-up form, but it should not have to, and a monthly seat licence makes little sense for software that calls a service in bursts.

Agent workloads are bursty and unpredictable. An agent might call a service 10,000 times in one hour during a site migration, then make zero calls for the next two weeks. Monthly subscriptions are a fundamental mismatch for this usage pattern. Per-call pricing fits because it aligns cost with actual consumption — nothing more, nothing less.

Stablecoins and agents solve complementary problems. Stablecoins provide programmable, instant settlement that software can trigger without human approval. Agents generate high-frequency, machine-speed demand that justifies always-on payment infrastructure. x402 bridges the two, creating a payment channel that works at the speed agents operate.

Coinbase’s x402 Bazaar adds a discovery layer on top. When a service completes a settled payment, the Bazaar auto-indexes it. Services with no settlement for 30 days get removed. This creates a living, merit-based catalog where agents can find services that actually work — understanding how AI agent frameworks handle tool selection and orchestration becomes essential context for anyone building agents that discover and consume x402 endpoints.

x402 vs Traditional API Payment Models

Four payment models dominate API access today. Each fails autonomous agents in a different way.

Of these models, x402 is the one where the payment travels with the HTTP request itself. Zero out-of-band setup. No account creation. No stored payment methods. No billing reconciliation.

The trade-offs are real. x402 payments are made in stablecoins, so the client needs a funded wallet or a service that pays on its behalf — which means wallet infrastructure and token management. The ecosystem is still early. But payments are settling over x402 today, including on Botonomy’s own endpoints, so “early” no longer means “theoretical.”

Practical Example: Agent-Callable SEO Audits via x402

Botonomy runs four x402-gated audit endpoints at pay.botonomy.ai, and Botonomy is listed in the x402 Bazaar: Schema Audit, On-Page Audit, AI-Citation Check, and Page Audit. This is first-hand operational experience — we built and maintain these endpoints in production.

Here is a concrete scenario. A development team is orchestrating a site migration across 2,000 URLs. Their AI agent needs to verify that each destination page maintains structured data integrity, on-page SEO signals, and AI-citation eligibility. The agent calls Botonomy’s Page Audit endpoint for each URL. It pays per call. It receives prioritised fixes ranked by impact.

No subscription. No onboarding. No sales call. The agent discovers the endpoint in the Bazaar, reads the 402 response headers, pays, and gets results.

One trust signal matters to agent builders: Botonomy’s endpoints do not charge the agent when a request returns an error. If the service fails, the agent keeps its money. Payment settles only after the audit succeeds, so agents pay for results, not failures.

The value proposition is metered, pay-only-for-what-you-use access to automated SEO audit systems. An agent running a 2,000-page migration pays only for the audits that complete; a request that returns an error costs it nothing. An agent checking a single page pays for one.

FAQ: Common Questions About the x402 Protocol

Can I buy x402 on Coinbase?

x402 is a payment protocol, not a cryptocurrency. Payments made over x402 use existing stablecoins, so there is nothing called x402 that the protocol asks you to buy.

Who invented x402?

x402 was incubated by the Coinbase Developer Platform team, and in September 2025 Cloudflare and Coinbase announced they were creating the x402 Foundation. The protocol builds on HTTP 402 Payment Required, originally defined in RFC 2068 in January 1997.

What is the Coinbase x402 AI payments protocol?

It is the same x402 standard: incubated at Coinbase, published as an open standard, and supported by Coinbase’s developer documentation and its x402 Bazaar discovery catalog.

What is the current price of x402?

x402 is a protocol, so it has no price of its own. What an agent pays is set per request by each service and paid in stablecoins. Any token trading under a similar name is a separate asset from the open standard.

What x402 Means for Service Businesses in 2026

The shift from per-seat to per-call pricing is not theoretical. Payments are already settling over x402 today.

Service businesses that expose x402 endpoints can be indexed in the Bazaar after their first settled payment, where agents search for them. Deliver value, get paid, stay listed. Go 30 days without a settled payment and the listing drops.

• Agent builders: Point your agent at pay.botonomy.ai or search “Botonomy” in the x402 Bazaar to access Schema Audit, On-Page Audit, AI-Citation Check, and Page Audit endpoints.
• Teams without an agent: Contact Botonomy to get a page audited — no agent required.
• Service providers: Read the x402 developer docs, stand up an endpoint, and let agent traffic find you.

The x402 protocol gave the internet a payment layer it has been missing since 1997. The agents are already using it. The question is whether your services are ready to be found.