CONCEPT

x402 / Pay-per-Crawl

Properties1
tagsagent-web, monetization, payments

2 min read

x402 / Pay-per-Crawl

Machine-to-machine micropayments built on the HTTP 402 “Payment Required” status code.

Definition

x402 is an open pay-over-HTTP protocol stewarded by the x402 Foundation (Cloudflare + Coinbase): client requests a gated resource → server returns 402 with payment details → client resubmits with payment authorization → a facilitator verifies and settles → resource is delivered. Pay per Crawl is Cloudflare’s first application: publishers set a flat per-request price and mark each AI crawler Allow/Charge/Block, with crawler identity anti-spoofed via Web Bot Auth (Ed25519 keys, RFC 9421 signatures) and Cloudflare as Merchant of Record. The Monetization Gateway generalizes it to any resource behind Cloudflare.

Key Properties

  • The request is the transaction — no accounts, checkout, or procurement.
  • Prices absurd for humans are fine for agents making thousands of calls.
  • Maturity (2026-08): Pay per Crawl is private beta; Monetization Gateway is waitlisted and settles only in stablecoins (Open USD/USDC, fiat via redemption); the fiat/subscription-friendly “deferred payment” scheme is an unfinalized proposal. x402 itself is usable now in Cloudflare’s Agents SDK and MCP servers.

Examples

  • Pay per Crawl’s reactive (402 → retry with crawler-exact-price) and proactive (crawler-max-price upfront) flows.
  • Per-lookup pricing as the end state of a Niche Data Refinery (report → dashboard → API → MCP → paid per lookup).

Application to the business

Not actionable day one in Port Huron — the general-purpose rails are waitlisted and crypto-settled. But x402-in-MCP is usable today, so an experimental paid MCP tool over local market data is technically possible now. Treat per-request revenue as the “run” phase, not a client promise.

Sources