x402: HTTP 402 Finally Gets a Job, at 32 Cents a Transaction

x402 takes the one HTTP status code that never found a job and makes it the handshake for machine payments. RFC 9110 §15.5.3 says the whole of what the standard has ever said about it: "The 402 (Payment Required) status code is reserved for future use." x402 supplies the use. A client requests a paid resource; the server answers 402 with the price; the client signs a stablecoin authorisation; a facilitator settles it; the server returns 200 with the content. No API key, no account, no prior relationship.

The governance is real and it is three weeks old

x402 launched via Coinbase in May 2025, but governance moved out. The Linux Foundation announced the operational launch of the x402 Foundation on 14 July 2026; the announcement states that "since the Foundation's intent to launch in April, 40 organizations have joined as members."

The premier members, read name-by-name off that announcement: Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe and Visa.

Two things follow. First, that roster is the payments industry rather than the crypto industry, which is the one structural difference between x402 and a decade of failed micropayment proposals. Second, the operating institution is twenty-two days old as of this writing, 5 August 2026 (the intent to form it dates to April 2026). Nothing about the members' balance sheets makes a three-week-old foundation an established rail.

It is not a competitor to AP2 — it is a settlement layer inside it

The common error is to list x402 alongside AP2 as rival standards. The relationship is vertical, and Google says so in its own words: "in collaboration with Coinbase, Ethereum Foundation, MetaMask and other leading organizations, we have extended the core constructs of AP2 and launched the A2A x402 extension, a production-ready solution for agent-based crypto payments."

AP2 supplies identity and cryptographically signed mandates — an Intent Mandate capturing what the user asked for, a Cart Mandate freezing the exact items and price. x402 answers "how do the funds move"; AP2 answers "who authorised this, up to what limit, with which merchants". A deployment with x402 and no mandate layer has solved the easy half — and a mandate is a spending limit, not a conduct limit (A Spending Limit Is Not a Conduct Limit).

The headline number is the platform's own counter — and it still deflates the story

x402.org's homepage displays, under the label "Last 30 Days": 75.41M Transactions, $24.24M Volume, 94.06K Buyers, 22K Sellers. That works out to an average transaction of about 32 cents.

Read the provenance before the number. Those figures are published by the protocol's own site, with no stated methodology, no named data source and no audit. CoinDesk's July 2026 report — the version most people have seen — sources them from x402.org rather than measuring anything, so it is republication, not corroboration. Treat the whole set as self-reported and as an upper bound.

That is what makes the conclusion safe. Even at the promoter's own most flattering figure, the aggregate is not yet a market. Against Visa's fiscal 2025 (its own annual report, page 19: "329 billion payments and cash transactions with Visa's brand were processed by Visa or other networks, equating to an average of 901 million transactions per day", and "Visa's total payments and cash volume was $17 trillion"), x402's self-reported ~2.5 million transactions a day is about 0.3% of Visa's transaction count, and its entire month of dollar volume is under a minute of Visa's. The 32-cent average is the point of a micropayment rail, not a defect — but a rail that moves $24 million a month is infrastructure, not revenue.

Three counters that do not agree, and why that matters

Anyone quoting x402 numbers is quoting one of at least three incompatible instruments:

| Figure | Basis | Who reports it | |---|---|---| | 75.41M tx, $24.24M, 94.06K buyers, 22K sellers | last 30 days | x402.org's own counter | | 169M payments, 590,000 buyers, 100,000 sellers | cumulative, "first year" | Coinbase (via InfoQ, July 2026) | | "well over 100 million cumulative transactions" on Base | cumulative through Q1 2026 | Chainalysis, 3 June 2026 | | 382,225 calls across 14,766 listings | last 30 days, one facilitator's discovery index | Salesmart S.r.l., which publishes Sinapsi, 3 August 2026 |

The first two cannot be reconciled casually: if 169 million payments is the first-year cumulative total as of July 2026, then a 75-million-transaction month would be roughly 45% of everything that ever happened on the protocol, in one month. Either growth is near-vertical or the two counters count different events. Neither reporter says which. The enumeration in the fourth row is our own: Salesmart S.r.l., which publishes Sinapsi, enumerated the CDP facilitator's discovery index on 3 August 2026 and counted the calls it reports. It is three orders of magnitude smaller because it measures a genuinely narrower thing — one facilitator's indexed listings, not all settlement — and we say so rather than pretending it refutes them (The x402 Market, Counted: 14,766 Listings, 12,741 Calls a Day, One Winner). The discipline: never place two of these four rows side by side without naming the basis.

What the composition data says, with its own defect

Chainalysis (3 June 2026) reports that "transactions of $1+ now represent 95% of total volume transferred, up from 49% in early 2025" — the best available evidence that the mix is shifting from noise toward commerce. Two caveats we are obliged to state. It is a composition statistic, not a growth statistic. And "early 2025" predates x402's May 2025 launch, an inconsistency inside the source itself that we could not resolve; the direction of travel is credible, the baseline date is not.

The same post explains what much of the earlier activity was: it attributes the late-2025 surge to PING, a meme coin whose pay-to-mint mechanic required small USDC payments over x402, "processing over 150,000 transactions in its first month" during a week in which the protocol surged "over 10,000%". Agents buying services and a token mint paying itself are both HTTP 402 traffic. Only one is an economy (The Earn-Spend Loop: Why Machine Payment Is Half-Built).

Where it actually shows up — and one correction

The distribution channel matters more than the protocol, and the two big edge vendors are at different stages.

AWS has shipped. On 15 June 2026 AWS announced AI traffic monetization as a new Bot Control capability: "AWS WAF returns a machine-readable HTTP 402 Payment Required response using the x402 open protocol for machine-to-machine payments", settling through Coinbase's x402 Facilitator with stablecoin payouts. In AWS's own words it is "available in all edge locations where AWS WAF Web ACLs are associated with Amazon CloudFront distributions" and comes "at no additional charge. Standard AWS WAF charges apply" — available today, no waitlist. (AWS does not use the words "generally available" or "GA" anywhere in that announcement, so neither do we: the availability facts above are the ones the contrast with Cloudflare actually rests on.)

Cloudflare has not. Its Monetization Gateway, announced 1 July 2026, will charge for "web pages, datasets, APIs, or MCP tools" with payments settling "in stablecoins over x402" — but the post says plainly that "the Monetization Gateway waitlist is open now for Cloudflare customers". A waitlist is an intention. Earlier drafts of this page, and much of the coverage, describe it as though it were live; it is not.

The seller-side difference is still the real one: x402 as a specification means implementing a facilitator and holding stablecoins; x402 behind a CDN means setting a price. AWS is the only one of the two where that is true today (Four Ways to Sell Content to an AI, and Who Keeps What).

Our thesis, stated so it can be falsified

Everything above is sourced. What follows is the judgement of Salesmart S.r.l., trading as Sinapsi, and should be attributed to us rather than to any source above.

Thesis. In 2026 the reason to price a resource over x402 is to make consumption countable, not to collect. The revenue is negligible; the meter is the asset.

Falsifiers. We are wrong if, by 30 June 2027, any of these hold: 1. x402.org's own 30-day dollar volume exceeds $500M (a >20x rise) — the rail would then be collecting, not just counting. 2. A named publisher or API vendor publicly reports >$1M in a year of x402-settled revenue, audited or in a filing. 3. Cloudflare's Monetization Gateway reaches general availability and a Cloudflare disclosure shows six-figure monthly settled volume through it.

We are also wrong in the other direction if by that date the x402.org counter has been withdrawn or restated downward, or if an independent audit shows the 30-day figure overstates settled economic payments by more than 2x.

For contrast on what a shipped agent-payment market actually looks like at volume, the comparison is not Silicon Valley (China Shipped Agent Payments First. The 1,000x Volume Gap Does Not Survive the Numbers.).