Skip to content
Insights
WeeklyAgentic Commerce4 min readHarrison Rolfes

The toll booth gets a standards body

In July the Linux Foundation announced the operational launch of the x402 Foundation and the completed contribution of the x402 protocol by Coinbase. Forty organisations joined at launch. The premier members read like the payments industry's org chart: Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Ripple, Shopify, Stripe and Visa, alongside the Solana, Stellar and Monad foundations and MoonPay.

Once Visa, Mastercard, Stripe and Google agree on how an agent pays, nobody gets paid for the protocol. Somebody still gets paid for knowing which agent is allowed to.

The protocol itself is plain. It revives the HTTP status code 402, Payment Required, reserved in the web's specification for three decades and never used. A client asks for a resource; the server answers 402 with the price and how to pay; the client signs a payment and sends it with the request; the server verifies it, directly or through a facilitator, settles it, and returns the resource with a receipt. The specification is network, token and currency agnostic, with implementations today across several blockchains and stablecoins, and the foundation's stated aim is to extend it to fiat as well.

Set it beside the rest of the year. Visa and OpenAI announced in June that Visa's payment capabilities would be integrated into OpenAI's experiences for agent-led payments. Mastercard's Agent Pay binds a tokenised card to a specific agent, merchant scope and consent policy. Visa's Trusted Agent Protocol signs an agent's identity into the request itself and lets the merchant check it against a directory. Google's AP2 shipped with more than sixty partners. Every one of these makes the same move: the network keeps the token and the consent record, and the transport becomes open.

That is the pattern we wrote the thesis for. When the rail is standardised by the people who own the rails, the money does not leave the category. It leaves the protocol and settles in the three things a transaction still has to pass through: proof of which agent is acting, proof of what its principal authorised it to do, and the settlement that a merchant will accept. Identity, authorisation, settlement. The toll is collected there, and a better model makes more agents transact, which makes the toll larger.

Sources

  1. 01Linux Foundation: Linux Foundation announces operational launch of x402 Foundation to standardize internet-native payments for AI agents and applications (2026-07-14)
  2. 02x402 Foundation on GitHub: the x402 protocol specification and payment flow
  3. 03CoinDesk: Visa, Stripe and Google join open-source project to let AI agents pay each other (2026-07-16)
  4. 04Digital Commerce 360: Visa, OpenAI work together to support agent-led payments (2026-06-12)
  5. 05Visa: Visa Intelligent Commerce, enabling AI agents to buy securely and seamlessly

Tell us what you are building. Every note gets a real read.