The Linux Foundation announced the operational launch of the x402 Foundation, a vendor-neutral governance body charged with standardizing the HTTP 402 payment protocol for AI agents and applications. Forty member organizations have signed on, including Ripple, Coinbase, Circle, and Binance. The foundation’s mandate is to maintain and extend an open payment standard that lets HTTP servers price individual responses and accept stablecoin settlement natively, without API keys, prepaid balances, or platform-specific integrations. Ripple’s simultaneous announcement that it joined the foundation to advance XRP and RLUSD for agentic payments on XRPL underscores how quickly the standard is being pulled into competing chain ecosystems.
How x402 Works Under the Hood
The x402 protocol repurposes HTTP status code 402, originally reserved for “Payment Required” but left unimplemented since the early web. The mechanism is straightforward in principle: a server returns a 402 response with a price denominated in a supported stablecoin, the client receives a payment challenge, and the agent signs a payment authorization that gets verified on-chain. If the payment is valid, the server releases the requested resource. The entire flow happens within standard HTTP request-response cycles, meaning agents do not need separate payment channels, session tokens, or accounts with each provider.
This matters for agentic commerce because the dominant payment model for API access today requires prepaid accounts or per-developer API keys, neither of which maps cleanly to autonomous agents that discover services dynamically, negotiate prices, and pay per-request. The 402 approach turns every HTTP response into a priced unit, which in theory scales to micro-transactions that traditional card networks and subscription billing cannot serve economically.
The Governance Question
Placing x402 under the Linux Foundation is a deliberate move to establish vendor neutrality. The standard was originally associated with Coinbase, which implemented it for USDC payments on Base, and early adopters were concentrated in that ecosystem. With 40 members now spanning issuers, exchanges, and infrastructure providers, the foundation structure is designed to prevent any single party from steering the protocol toward its own stablecoin or chain.
Whether that governance holds in practice remains an open question. Circle has its own open source Agent Stack for USDC, Binance is implementing x402 on BNB Chain, and now Ripple wants RLUSD positioned alongside USDC for x402 flows on XRPL. Each issuer has commercial incentives to make their stablecoin the default settlement asset. The foundation’s technical working groups will need to define neutral settlement interfaces that do not privilege any one token, or the standard fragments into chain-specific implementations.
Ripple, XRPL, and the Multi-Chain Race
Ripple’s entry into the x402 Foundation coincides with XRPL surpassing one million AI agent transactions on its mainnet, according to the network’s own reporting. That number is early and the transaction types are not fully specified, but it signals that XRPL is positioning itself as a settlement layer for agentic commerce alongside Base, Solana, and others. Ripple’s RLUSD stablecoin, launched late last year, would be the natural settlement asset for x402 flows on XRPL.
Binance confirmed separately that its agentic payments infrastructure on BNB Chain now supports x402 payment flows, giving agents the ability to pay for online services automatically. The convergence of Coinbase, Binance, and now Ripple around the same standard suggests the industry has settled on HTTP-native payments as the interoperability layer for machine-to-machine commerce. The unresolved tension is which chain and which stablecoin capture the settlement volume.
What to Watch
The foundation’s first technical deliverables will indicate whether the standard evolves toward genuine multi-chain settlement or fractures into parallel implementations. Key signals include whether the working groups publish a reference implementation that supports multiple stablecoins and chains out of the box, or whether each member ships its own flavor. Transaction volume on XRPL and BNB Chain attributable to x402 flows is worth tracking against Base’s early lead. And the inclusion of non-stablecoin assets like XRP in the settlement design raises questions about volatility exposure that pure stablecoin settlement avoids.