Kunzum  /  Blog  /  Coinbase built x402 and gave it away. What does it still control?

Coinbase built x402 and gave it away. What does it still control?

Coinbase handed the x402 specification and economics to the Linux Foundation's x402 Foundation, but kept key operational layers: the CDP facilitator, seller docs, and Agent.market discovery. Neutral governance is the entry ticket, not full neutrality.

Agentic payments6 min read

Coinbase built x402 and gave it away. What does it still control?

In short

  • The Linux Foundation announced the x402 Foundation on 2 April 2026 and launched it on 14 July 2026 with 40 member organisations and 17 premier members.
  • Coinbase transferred the x402 specification and no-fee protocol economics to the Foundation, but kept the CDP facilitator, seller documentation, and Agent.market discovery.
  • CDP says its facilitator has processed more than 100 million x402 payments.
  • Public data shows uneven demand: daily x402 transactions fell from about 731,000 in December 2025 to about 57,000 in February 2026.

This is part of the Kunzum reference on What is x402? The plain-English guide to agentic payments, which carries the figures this post draws on and the date each one was checked.

What Coinbase actually handed over

Two dates matter.

On 2 April 2026, the Linux Foundation announced at the MCP Dev Summit North America in New York that it was launching the x402 Foundation, with Coinbase contributing the x402 protocol. The operational launch came on 14 July 2026 with 40 member organisations and 17 premier members: Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe and Visa.

That is a card network list, a cloud list and a payments list in one row. Companies of that size do not sign a governance charter to appear in a press release.

What transferred is the specification. The protocol repository holds the specs directory, the payment schemes including the exact scheme that transfers a specific amount, the PaymentPayload and PaymentRequirements objects, the facilitator role, and reference SDKs and middleware for TypeScript, Python and Go.

The economics transferred too. The x402.org documentation states that the protocol charges no fee of its own and that payers cover network fees only. No protocol-level cut, no take rate, and the spec is blockchain-agnostic across EVM chains and Solana. If you are checking whether the handover was real, that part holds up.

What stayed with Coinbase

Nobody publishes facilitator market share, so the honest answer to "how much of x402 runs through Coinbase" is that the data does not exist in public. What exists is the shape of the stack.

Three layers did not move.

  • The facilitator. Coinbase Developer Platform runs a facilitator that verifies and settles payments, on Base and Solana, and its seller-facing documentation states CDP has processed more than 100 million x402 payments. The protocol defines the facilitator role; it does not require Coinbase to fill it. In practice most implementations start with the one already wired into the account they use for everything else. What is an x402 facilitator, and do you need one? covers what the role actually involves.
  • The documentation developers read. x402.org is the standard. The CDP docs are where sellers go to accept a payment. That is a distribution channel, and it belongs to one member.
  • The discovery layer. Coinbase published its own cumulative count in late April 2026, roughly 165 million transactions, about $50 million of volume and 69,000 active agents, in the week Agent.market launched (CoinDesk, via Yahoo Finance). A directory of agents, run by the company that also runs the settlement path those agents use, is a position.
LayerWho operates itUnder Foundation governance
Protocol specificationx402 FoundationYes
CDP facilitator (verify, settle)CoinbaseNo
Seller documentation on CDPCoinbaseNo
Agent.market discoveryCoinbaseNo
Reference SDKs and middlewareCoinbase repositoryNo

Why enterprises needed the handover first

The premier member list is the tell. Adyen, American Express, Mastercard, Visa and Stripe settle card traffic for a living. None of them signs up to route agent traffic through a rail whose specification, roadmap and default facilitator all sit with a single crypto exchange. Moving the spec to the Linux Foundation removes that objection at the specification layer. It leaves the operational layer where it was.

Neutral governance is the entry ticket. It gets a payment rail into procurement conversations at companies that would otherwise run a legal review and stop. It does not make the rail neutral.

The demand question is separate, and the governance story tends to paper over it. Citing Artemis, CoinDesk reported in March 2026 around $28,000 of real daily x402 volume, an average payment of about $0.20 and roughly 131,000 daily transactions. Chainalysis counted well over 100 million cumulative x402 transactions on Base through Q1 2026 and found payments of $1 or more rose from 49% of value in early 2025 to 95% by early 2026. TRM Labs measured 198.9 million settlements and $52.7 million of total value since May 2025, screening to $25.62 million of plausible commerce, of which 0.6% to 7.5% appears agentic, with 99.6% of that value settled in USDC.

Volume has been lumpy. Daily x402 transactions fell from about 731,000 in December 2025 to about 57,000 in February 2026, a decline of over 92%, per BlockEden.xyz. Chainalysis attributes part of the earlier spike to PING, a pay-to-mint experiment that lifted transactions over 10,000% in one week. If you want the raw material behind those numbers, the Kunzum research corpus keeps the responses and scoring scripts.

Cloudflare joined as a premier member and also runs its own commercial layer. It published the Monetization Gateway on 1 July 2026, letting customers charge for any protected asset, from pages and datasets to APIs and MCP tools, settling in stablecoins over x402. It separately runs Pay Per Crawl, which prices crawler access using HTTP 402 with Cloudflare as merchant of record. Cloudflare sits in front of 25.8% of all websites (W3Techs, September 2026 survey), and its chief strategy officer said the network sends over a billion HTTP 402 responses a day, a remark quoted by CoinDesk on 5 May 2026.

The foundation is a room full of companies that each intend to operate something. That is the normal outcome for a neutral standards body. It is also why "the protocol is decentralised" and "the market is competitive" are separate claims.

What would actually signal capture

Watch these, in rough order of how much they would matter.

  1. Facilitator concentration. If the Foundation starts publishing share by facilitator and one name holds most of it, spec governance buys less than it appears to. Today no such figure is published, which is itself the gap.
  2. Where the canonical docs live. A standard whose integration guide lives on one member's domain has outsourced its on-ramp.
  3. Who controls discovery. If agents find services through one registry, whoever ranks that registry controls demand, regardless of who owns the spec.
  4. The change process. Whether a non-Coinbase member can get a payment scheme merged without Coinbase's approval. The repository history is public, so this is checkable.
  5. Fees at the edge. The protocol charges nothing. If a facilitator layer introduces a take rate and volume concentrates in few facilitators, the free-protocol claim survives on paper and dies in practice.
  6. Whether the premier 17 ship. Seventeen logos dated 14 July 2026 mean little until more than a handful show production volume.

The correct summary is narrow. Coinbase gave away the specification, on a documented date, to a foundation that now has 40 members. It kept the facilitator, the developer on-ramp and the discovery layer. Nothing about the handover requires you to assume bad faith, and nothing about it makes the stack neutral. If you want to see how answer engines describe this arrangement when people ask them, what AI recommends instead is where to compare.

Questions

What did Coinbase actually hand over with x402?

Coinbase contributed the x402 protocol specification to the x402 Foundation. The transferred specification includes the specs directory, payment schemes such as the exact scheme, PaymentPayload and PaymentRequirements objects, the facilitator role, and reference SDKs and middleware for TypeScript, Python and Go. The economics transferred too, with no protocol fee and payers covering network fees only.

What parts of x402 stayed with Coinbase after the handover?

The CDP facilitator, seller documentation on CDP, and Agent.market discovery stayed with Coinbase. The post's table also lists reference SDKs and middleware in the Coinbase repository as not under Foundation governance. The protocol specification is under x402 Foundation governance.

Why did enterprises need the x402 handover first?

Premier members such as Adyen, American Express, Mastercard, Visa and Stripe settle card traffic for a living. None of them signs up to route agent traffic through a rail whose specification, roadmap and default facilitator all sit with a single crypto exchange. Moving the spec to the Linux Foundation removes that objection at the specification layer, but the post says it leaves the operational layer where it was.

Sources

Published 2026-09-20. Written by Narender Charan, who runs Kunzum.