x402 lets a web service price a request inside HTTP itself. The server answers with 402 Payment Required and machine-readable payment terms. The client signs a payment authorization and retries. Once the payment is verified and settled, the service returns the resource. For AI agents this means an API call, a dataset or an inference request can be paid for per use, with no account signup, API key or invoice.
x402 is only the payment-and-access exchange. It is not a compute marketplace, a scheduler or a GPU provider. It does not allocate capacity, pick hardware or measure your workload. “Agents that pay for compute” therefore means agents paying services that sell compute-backed results, such as inference endpoints and compute-heavy APIs. The protocol supplies the billing handshake, and the service supplies the compute.
As an Amazon Associate I earn from qualifying purchases.
How an x402 payment works, step by step
Coinbase Developer Platform’s x402 whitepaper describes the general flow. Its abstract calls x402 “an open payment standard that enables AI agents and web services to autonomously pay for API access, data, and digital services.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Request. A client asks for a protected HTTP resource.
- Challenge. The server replies with
402 Payment Requiredand payment requirements. Depending on the implementation, these include the amount, the accepted asset or method, the network and the destination details. - Authorization. The client builds and signs a payment authorization, then retries the same request with the payment information attached.
- Verification and settlement. The server, or a facilitator acting for it, verifies the authorization and handles settlement.
- Delivery. If verification and settlement succeed, the server returns the resource. It may also return a payment receipt or response header.
Cloudflare’s Agentic Payments documentation puts it this way: “Agentic payments let AI agents purchase resources and services directly through the HTTP 402 Payment Required response code.”
Header names depend on the protocol version
Cloudflare’s x402 version 2 documentation uses three headers: PAYMENT-REQUIRED for the challenge, PAYMENT-SIGNATURE for the client’s signed retry, and PAYMENT-RESPONSE for the outcome. Header names and details vary by protocol version and implementation. If you read examples from several sources, check which version each one targets before mixing them in one codebase.
What “paying for compute” does and does not mean
The protocol puts a price into the HTTP exchange. Coinbase says developers can use variable-rate pricing for usage-based workloads such as inference or compute-heavy API calls. That is the whole connection to compute.
Consider an agent calling a paid inference or data API. The server states a price and payment requirements. The agent checks the price against its budget and policy and decides whether to authorize it. The service responds after payment verification. This is an illustration of the mechanism. It is not evidence that any particular compute provider accepts x402 today.
Recommended Free Tools
x402 leaves these things to the service and its infrastructure:
- allocating or reserving compute and guaranteeing capacity;
- choosing hardware such as a GPU;
- measuring what a job actually consumed, which matters if the quoted price should track real usage;
- deciding what happens when a job fails after payment.
Who supports it: the implementation landscape
| Player | What is documented | Caveat |
|---|---|---|
| Cloudflare | The Agents SDK documents x402 over HTTP and MCP, with server middleware and an x402-aware client. Cloudflare also documents a proxy pattern that gates an HTTP backend behind payment. | In its proxy example, base-sepolia is a test network and base is production. Do not copy test configuration into production. |
| Coinbase | The Coinbase x402 Facilitator is described as handling on-chain verification and settlement, including in the AWS publisher integration. | A facilitator spares a service from talking to a blockchain directly, but it becomes part of your trust and operations design. |
| AWS (via Coinbase) | Coinbase’s June 2026 announcement describes an integration for publishers that uses Amazon CloudFront and AWS WAF to put payment challenges in front of agent traffic. | This is a vendor account of a product integration, not an independent study of adoption or performance. Its line that roughly a quarter of the internet runs on CloudFront and WAF describes AWS’s reach, not x402 usage. |
Governance
In September 2025 Cloudflare announced its intent to create an x402 Foundation with Coinbase. Matthew Prince, Cloudflare’s co-founder and CEO, said in that announcement: “The Internet’s core protocols have always been driven by independent governance, which is why we’re proud to work with Coinbase to ensure x402 has the same path, given its likelihood to become a core protocol for agentic commerce.” That is a company’s opinion, not an established forecast. Coinbase’s June 2026 account describes x402 as an independent Foundation under the Linux Foundation. That is the more recent description, and it comes from Coinbase. The earlier announcement should not be read as the current status.
What nobody has shown yet
The official sources reviewed contain no independently verified adoption figure, no aggregate x402 transaction volume and no head-to-head performance benchmark. Treat any such number you meet elsewhere with caution unless its origin is clear.
x402 versus MPP
Cloudflare documents a second protocol, the Machine Payments Protocol (MPP). Its overview contrasts the two as follows.
Free tools Windows power users keep installed
One-click scans. No signup required.
| x402 | MPP | |
|---|---|---|
| Payment methods | On-chain stablecoins | Multiple methods, including Stripe card payments and stablecoins |
| Headers | PAYMENT-REQUIRED, PAYMENT-SIGNATURE, PAYMENT-RESPONSE (v2) |
WWW-Authenticate: Payment and Authorization: Payment |
| Interoperability | Not stated | MPP clients can consume existing x402 services, per Cloudflare |
This comparison reflects Cloudflare’s documented ecosystem. It does not show that either protocol is better overall.
Axes for choosing an implementation
- Payment methods and networks: which assets, chains or card rails the implementation really supports.
- Integration surface: HTTP only, MCP tools, or both, and which server middleware and client SDKs exist.
- Settlement and trust: who verifies payment, submits transactions, handles failures and issues receipts.
- Pricing model: per request, variable usage, batches or recurring access.
- Security controls: how an authorization is bound to a specific request and protected from replay or tampering.
- Operational fit: latency, transaction cost, failure behavior, refunds or disputes, and availability for your actual service.
Security: what researchers have found
A May 2026 arXiv preprint by Zelin Li, Qin Wang and Zhipeng Wang reports five attacks. They involve authorization, binding, replay protection and web-layer handling. The authors describe reproducible tests on local chains, Base Sepolia and live endpoints, plus audits of three open-source SDKs and endpoints. It is a preprint, and the findings concern the designs and implementations the authors tested. They do not show that every deployment is exploitable. They do show that credential validation, request binding, replay protection and failure handling deserve explicit design work.
Questions to settle before letting an agent spend
The sources describe integration patterns but do not settle operating policy for a particular deployment. If you run a paid endpoint or an agent that pays, decide these in advance:
- Payment settles, service fails. Does the client get a retry, a refund or nothing? x402 does not answer this for you.
- Spending limits. Where does a per-request cap, a daily budget or a human-approval threshold live, and what happens when a server quotes a price above it?
- Wallet permissions. What credentials or signing authority does the agent hold, and how large is the loss if they leak?
- Test versus production. Keep test-network settings, such as
base-sepoliain Cloudflare’s example, out of production configuration. - Facilitator dependence. If a facilitator verifies and settles payments, consider what happens when it is unavailable or wrong.
Where this leaves you
x402 is worth evaluating if you sell a metered digital resource to software clients and want to drop signup flows and keys. It is also worth evaluating if you build agents that must buy such resources unattended. Build the spending policy and the failure handling yourself. Check the protocol version your tooling targets. Verify claims of scale independently, because the public evidence for ecosystem size is so far mostly vendor-reported.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
