402 - Payment Required

How will autonomous AI agents pay for things online? The answer lies in a 30-year-old, forgotten HTTP status code.

#1about 3 minutes

The long history of the undefined 402 status code

The `402 Payment Required` HTTP status code has been reserved for future use for three decades, despite early attempts like CyberCash and JEPI to define a standard.

#2about 2 minutes

Recent attempts at web payment standardization

Modern efforts like the Payment Request API and Web Monetization have tried to address web payments but have not resulted in a universal standard for the 402 status code.

#3about 6 minutes

Understanding the first frontier of digital payments

The payments landscape has shifted dramatically, with digital methods like account-to-account transfers, digital wallets, and stablecoins now dominating e-commerce.

#4about 4 minutes

The new frontier of agentic and autonomous commerce

AI agents require new payment infrastructure, with autonomous agents needing atomic, programmable, and permissionless transactions with immediate settlement.

#5about 4 minutes

Current competing proposals for web payment protocols

In the absence of a standard, companies like Cloudflare and Coinbase are creating proprietary or divergent solutions like Pay per Crawl and X402 to handle machine-to-machine payments.

#6about 2 minutes

A call to action for a unified open payment standard

The industry needs to collaborate on a universal, open standard for web payments to support the future of autonomous commerce, rather than relying on fragmented solutions.