Linux Foundation Launches x402 Foundation With 22 Industry Backers as AI Agent Payment Infrastructure Takes Shape
Coinbase donates its x402 protocol to the Linux Foundation, joining Stripe's competing MPP standard in a race to build the payment layer for autonomous AI agents.
Overview
The Linux Foundation announced the x402 Foundation on April 2, 2026, during the MCP Dev Summit North America in New York. Coinbase formally donated the x402 protocol to the new foundation, which will govern development of an open standard that repurposes the long-dormant HTTP 402 “Payment Required” status code as a native payment layer for AI agents, APIs, and web applications.
The move follows Stripe’s launch of its own Machine Payments Protocol (MPP) on March 18, together establishing two competing but complementary standards for a problem that barely existed a year ago: how autonomous software agents should pay for the services they consume.
What x402 Does
The x402 protocol embeds payment logic directly into HTTP interactions. When an AI agent requests a paid resource, the server returns a 402 status code with payment instructions. The agent reads those instructions, settles the transaction using USDC on Base or Solana, attaches proof of payment to a retry request, and receives the resource --- all without human intervention.
The protocol supports transactions as small as $0.01 and is designed for the kind of high-frequency, low-value API calls that characterize agentic workflows: data lookups, compute requests, content access, and tool invocations within Model Context Protocol pipelines.
According to the Linux Foundation press release, 22 organizations have expressed support for the foundation, including Adyen, Amazon Web Services, American Express, Circle, Cloudflare, Fiserv Merchant Solutions, Google, KakaoPay, Mastercard, Microsoft, Polygon Labs, Shopify, Solana Foundation, Stripe, and Visa. The Solana Foundation has accounted for approximately 65 percent of x402 transaction volume to date.
“The internet was built on open protocols,” Linux Foundation CEO Jim Zemlin said in the announcement. “The x402 Foundation creates a community-governed home ensuring transparent evolution with broad ecosystem participation.”
Stripe’s Competing Standard
Two weeks before the x402 Foundation launch, Stripe introduced the Machine Payments Protocol, an alternative approach co-authored with Tempo, a payments-focused Layer 1 blockchain incubated by Stripe and Paradigm. Tempo launched its mainnet on the same day, March 18.
Where x402 settles each transaction individually on-chain, MPP uses session-based streaming payments: an agent authorizes a spending limit upfront and streams micropayments against that session without a separate blockchain transaction for each API call. MPP also supports fiat payments through Shared Payment Tokens, enabling agents to pay with credit cards and buy-now-pay-later methods alongside stablecoins.
Stripe’s design partners for MPP included Visa, Mastercard, Deutsche Bank, Standard Chartered, Revolut, Nubank, Shopify, OpenAI, Anthropic, Ramp, and DoorDash, according to Fortune. Tempo raised $500 million at a $5 billion valuation in 2025 from investors including Paradigm and Joshua Kushner’s Thrive Capital.
Stripe itself supports both protocols. Its machine payments documentation lists x402 alongside MPP as supported payment methods, with x402 handling USDC on Base and Solana, and MPP operating on the Tempo network as well as traditional card networks.
What We Don’t Know
The long-term viability of either standard remains unproven. The x402 protocol has recorded roughly 131,000 daily transactions averaging $0.20 each, but approximately half of that volume appears to be testing activity rather than production usage. MPP launched too recently for meaningful volume data.
It is also unclear whether two competing standards will coexist, converge, or whether one will dominate. The protocols address the same problem with fundamentally different architectures: x402 prioritizes openness and per-request settlement, while MPP prioritizes session efficiency and integration with Stripe’s existing compliance and fraud detection infrastructure.
The geographic limitations add further uncertainty. Stripe’s machine payments are currently available only to US-based developers, excluding New York and Texas, which restricts early adoption.
Why It Matters
The emergence of dedicated payment infrastructure for AI agents marks a structural shift in how APIs are monetized. Traditional payment systems require human decision points --- login screens, checkout flows, card entry forms --- that autonomous agents cannot navigate. Both x402 and MPP eliminate those friction points, enabling per-request billing at scales that were previously impractical.
For API developers, this opens new monetization models. Services that previously required subscription plans or API key quotas can now charge agents per call, with transactions settling in seconds at costs measured in fractions of a cent. The early use cases highlighted by Stripe --- agents paying for headless browser sessions, physical mail printing, and even sandwich orders --- suggest the scope extends well beyond traditional software services.
The involvement of major payment networks (Visa, Mastercard, American Express) and cloud providers (AWS, Google, Microsoft) on both sides of the standards competition signals that the industry views agent-to-service payments as an inevitable infrastructure layer rather than a speculative experiment.