x402 and the Machine Payments Protocol standardize how AI agents pay each other
The rails for machine commerce are standardizing. The x402 standard revives HTTP's 402 'Payment Required' status to let agents embed payment terms directly in web requests, while Stripe and Tempo launched a Machine Payments Protocol for agent-to-agent transactions — and Visa's Intelligent Commerce and Mastercard's Agent Pay test agent-initiated purchases under preset limits.
Reviving HTTP 402 is an elegant move. The 'Payment Required' status code has sat unused in the web's specification for decades; x402 turns it into the mechanism by which an agent and a service negotiate payment inline, so a paid API or resource can be accessed automatically without a human checkout. It makes payment a native part of a web request rather than a separate flow.
The proliferation of protocols — x402, Stripe and Tempo's MPP, Visa and Mastercard's agent flows — signals the plumbing is being built in earnest, but also that no single standard has won yet. Multiple protocols competing to be the rails for agent commerce is what an early-but-serious market looks like; the winner will be whichever the ecosystem coalesces around.
The governing constraint remains authorization. Every one of these systems is built around agents acting under predefined limits and delegated authority — because the hard problem was never moving the money but bounding what an agent may spend and proving who approved it. The rails are arriving; the trust framework around them is the work that decides whether machine commerce scales safely.
Sourcetrail — AI agents in 2026: protocol updates, enterprise tools, autonomous payments → · Fenwick — Is 2026 the year of agentic payments? →