The Linux Foundation has announced the creation of the x402 Foundation, an industry group that will manage the x402 payment protocol, an open standard intended to let AI agents, applications and APIs pay for digital services directly over HTTP.
What the x402 protocol adds to web transactions
The protocol, first developed by Coinbase, embeds payment functions into standard web requests. Instead of routing payments through separate checkout pages or billing platforms, developers can include payment data in an HTTP request that uses the 402 “Payment Required” status code. The specification supports both traditional card payments and stablecoin cryptocurrencies, aiming to avoid vendor lock‑in.
According to the foundation’s statement, the open structure lets developers, financial institutions, cloud providers and other members shape the protocol collaboratively. This governance model is meant to keep the payment layer neutral and adaptable.
Industry backing and early adoption
Since the project was announced in April, forty organizations have signed on, including Amazon Web Services, Google, Visa, Mastercard, Stripe, American Express, Cloudflare, Coinbase, Fiserv, Ripple and Shopify. These members span cloud providers, payment networks and financial‑technology firms, reflecting a broad interest in standardizing machine‑to‑machine commerce.
Adoption will depend on developer ease.
The protocol targets a gap that many developers notice: today, monetizing APIs and online services typically involves subscriptions, prepaid credits or custom billing integrations. By allowing payment information to travel with the same HTTP request that calls an API, the x402 standard could simplify the process for both providers and consumers.
Related: AI agents set to transform governance strategies
While the foundation’s statement emphasizes security and flexibility, the real test will be whether the protocol gains traction beyond the initial consortium. Historically, the HTTP 402 status code has seen limited use, and adoption will depend on the ease of integrating the standard into existing development stacks.
How the protocol works in practice
When an AI agent or application needs to access a paid service, it can issue an HTTP request that includes payment credentials. The server responds with a 402 status, indicating the amount required and the accepted payment methods. The client then resubmits the request with payment details, completing the transaction without invoking a separate checkout flow.
This approach is designed for a range of use cases, from paid AI APIs and cloud compute resources to digital content and other online services that require per‑use fees. By standardizing the interaction, the protocol aims to reduce the need for bespoke billing solutions.
The foundation says the protocol can handle multiple payment types, including traditional cards and stablecoins, and that it will evolve through contributions from its member organizations. Implementation guidance and future extensions are expected to be published as the consortium works on the specification.
Overall, the x402 Foundation seeks to provide a neutral home for the protocol, ensuring that technical specifications remain open and that the payment layer of the internet stays interoperable. The Linux Foundation and Coinbase have not offered additional comments as of the time of publication.
