The x402 payment protocol lets AI agents pay websites directly when they request paid content, a change that could shift how publishers monetize answers provided by generative AI.
How the x402 payment protocol works
Coinbase introduced the x402 payment protocol in May 2025 to let websites price articles, data sets, APIs, and other resources for automated clients, or AI agents. When an agent requests paid content the website can respond with an HTTP 402 payment required message that lists the price, accepted tokens, blockchain network, and a receiving address.
The AI agent signs a payment authorization with a crypto wallet and reissues the request with the signed authorization. The site can verify the signature itself or send it to a payment service to validate and settle, then deliver the content, all without sending the user to a separate checkout page.
How sites and agents manage access and billing
Cloudflare has built Monetization Gateway tooling compatible with x402 that is aimed at single-request services, such as fetching a market data point or generating a PDF. Settlements in those tests have used USDC stablecoin on the Base blockchain. Sites can set fixed prices, authorize a spending cap, or bill after the fact based on verified usage.
Cloudflare also tested a Pay Per Crawl feature in July 2025 that lets operators control and charge for how often crawlers access content. That system charges by crawl count, so if an article is crawled once but later reused many times inside AI answers, subsequent uses require a separate Pay Per Use arrangement.
Pay Per Use and fixed contracts
For content that can be quoted or cited repeatedly, Cloudflare and others expect Pay Per Use contracts where verified buyers report and pay for each reuse. Fixed-fee agreements let a buyer sign for a set amount up front, while usage-based contracts authorize a maximum and then bill for actual consumption.
Existing examples include Stocktwits selling per-request market sentiment data, and Cloudflare offering per-inference billing for specified models to U.S. customers through its AI Gateway. Operators must ensure agents have funded wallets, and buyers must set spending limits before transactions proceed.
Adoption and transaction volume for x402
As of Nov. 11 AgentEconomy tracked about 199 million x402 transactions, with cumulative settled volume near $42.5 million (originally 333 million HKD), covering payments for data, model computations, and related services.
Those totals show that the x402 payment protocol is already in active use across data providers and gateway services, though monetization models vary between one-time access and repeated-use arrangements. Industry operators and publishers are still testing how to balance discoverability with direct monetization when AI agents can answer user queries without a human clicking through to the source.
Publishers that rely on advertising and subscriptions face the risk that answers compiled by AI will reduce site visits even when the content is being read. The x402 payment protocol offers a direct revenue path, but it also requires publishers to implement access controls and to choose settlement partners or systems that match their business model.
Cloudflare documented its Monetization Gateway beta and Pay Per Crawl experiment in a company blog post, and Coinbase published information about the x402 protocol on its x402 project page. AgentEconomy provided the transaction tracking cited here.
