On July 14, 2026, the Linux Foundation completed the operational launch of the x402 Foundation, formally taking over stewardship of the x402 protocol from Coinbase. The protocol is named after HTTP's dormant "402 Payment Required" status code and is built to let software transact without bolting payments on as an afterthought. What it does: x402 embeds secure payment capabilities directly into web interactions so that AI agents, APIs, and applications can send and receive payments as seamlessly as they exchange data, with support for payment types ranging from traditional cards to stablecoins. That matters for agent orchestration specifically — an agent that needs to call a paid API, hire another agent for a subtask, or settle a transaction mid-workflow has historically had to fall back on human-mediated checkout flows or bespoke billing integrations. x402 tries to make payment a native part of the HTTP request-response cycle itself, so a coordinating agent can hit a paywalled endpoint and settle the cost in the same exchange that fetches the resource. The governance shift is the more interesting part of the news. Coinbase has formally transferred the protocol to the foundation, placing it under vendor-neutral control for the first time. This is a deliberate move away from single-vendor control at a moment when the protocol has real traction: 40 organizations, including Coinbase, Circle, Visa, and Mastercard, have joined since the effort's April intent-to-launch. Premier members span the length of the payments and infrastructure stack — Adyen, AWS, American Express, Circle, Cloudflare, Fiserv, Google, Mastercard, Solana Foundation, Stripe, and Visa among them — alongside a general membership that includes blockchain infrastructure firms like LayerZero Labs and Polygon Labs. The framing from the Linux Foundation is explicit about why this matters for machine-to-machine coordination: AI agents and automated systems are becoming active participants in the global economy, yet they have lacked a native, secure way to transact. Handing a payment protocol to a neutral standards body rather than leaving it under a single company's control is the same pattern that's played out with other agent-facing infrastructure this year — the bet is that agents transacting across organizational boundaries need a settlement layer nobody can unilaterally change the rules on. Whether x402 becomes the de facto default for agent-initiated payments, or one of several competing standards, will depend on adoption outside this initial member roster over the next few quarters.