Kunzum  /  Blog  /  Cloudflare Pay Per Crawl: how it works and who gets paid

Cloudflare Pay Per Crawl: how it works and who gets paid

Cloudflare Pay Per Crawl puts a price on crawler access and returns HTTP 402 instead of the page. Cloudflare is merchant of record, and the launch post describes a private beta, so this is not a switch every site can flip.

Agentic payments6 min read

Cloudflare Pay Per Crawl: how it works and who gets paid

In short

  • Cloudflare's launch post describes Pay Per Crawl as a private beta: the publisher sets a price, Cloudflare answers crawlers with HTTP 402 and acts as merchant of record.
  • x402 is the general payment protocol under Cloudflare's Monetization Gateway. It charges no fee of its own and supports EVM chains and Solana; payers cover network fees only.
  • The broader Monetization Gateway was published 1 July 2026 for any protected asset, settling in stablecoins over x402, while AI Crawl Control is already shipped.
  • Cloudflare measured nearly 71,000 crawls per referral for Anthropic in the week of 19 to 26 June 2025, 1,600 to 1 for OpenAI, 202.4 to 1 for Perplexity, 40 to 1 for Microsoft, and 9.4 to 1 for Google.

This is part of the Kunzum reference on What is x402? The plain-English guide to agentic payments, which carries the figures this post draws on and the date each one was checked.

Pay Per Crawl in one paragraph

Cloudflare's Pay Per Crawl puts a price on crawler access and makes Cloudflare the merchant of record, with the HTTP 402 status code carrying the request for payment. Cloudflare's launch post describes it as a private beta. That word matters more than the launch coverage suggested: it is not a setting every Cloudflare site can switch on, so check your own dashboard before planning around it.

The flow, request to settlement

As published, the flow is four steps.

  1. A crawler requests a URL that sits behind Cloudflare.
  2. Cloudflare returns 402 instead of the asset.
  3. The crawler settles, or does not.
  4. Cloudflare, as merchant of record, releases the asset.

The launch post describes the payment request as HTTP 402 with Cloudflare as merchant of record. It is easy to assume that means x402, the open protocol that carries 402 payments, but the launch post does not say so, and this post will not either. x402 is what Cloudflare's later Monetization Gateway settles over. According to the x402 documentation, that protocol charges no fee of its own: payers cover network fees only. It is blockchain-agnostic, supporting EVM chains and Solana. Kunzum has written before about who built it and why the handover happened.

What the crawler sees in the 402 is the part worth understanding. It is a payment request, not a block page. A crawler built to read it can decide a price is acceptable and pay without a human in the loop. A crawler that is not gets nothing.

What happens when a crawler declines to pay is not something Cloudflare has published in the posts it has made public. The fallback could be a block, a downgraded response, or nothing at all. Treat any confident account as unverified.

Who gets paid, and who holds the money

The publisher sets the price. Cloudflare is merchant of record, which means the payment relationship runs through Cloudflare rather than directly between the site and the crawler. Pricing sits on top of the sibling product, AI Crawl Control, which lets publishers see and sort AI crawlers by purpose instead of blocking the category wholesale.

Where x402, the Monetization Gateway and Pay Per Crawl sit

ProductWhat it charges forStatusSettlement
Pay Per CrawlCrawler access to a site's contentPrivate betaHTTP 402, Cloudflare as merchant of record
AI Crawl ControlNothing. It classifies crawlers by purposeShippedNone
Monetization GatewayAny protected asset: pages, datasets, APIs, MCP toolsPublished 1 July 2026Stablecoins over x402

Pay Per Crawl is a specific application. The Monetization Gateway is the general layer: it lets Cloudflare customers charge for any protected asset, settling in stablecoins over x402, per Cloudflare. Note the date on that post. It went up on 1 July 2026.

Governance of the protocol moved at the same time. The x402 Foundation went operational on 14 July 2026 with 40 member organisations, and the 17 premier members include Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe and Visa, per the Linux Foundation.

The cost side: what charging does to retrieval and citation

Charging a crawler is a revenue decision and a visibility decision at once.

The scale of crawling is not in dispute. Cloudflare sits in front of 25.8% of all websites as of the September 2026 W3Techs survey. Its chief strategy officer said in May 2026 that the network sends over a billion HTTP 402 responses a day, quoted by CoinDesk.

The crawl-to-referral ratios are the number to hold in your head. For the week of 19 to 26 June 2025, Cloudflare measured nearly 71,000 crawls per referral for Anthropic, 1,600 to 1 for OpenAI, 202.4 to 1 for Perplexity, 40 to 1 for Microsoft and 9.4 to 1 for Google. Those are 2025 figures, and they have improved by more than an order of magnitude since. They still describe a lopsided trade.

Then there is the retrieval side. Kunzum's own measurement of edition-one answers found ChatGPT retrieved on 54% of answers (65 of 120), Claude on 65% (78 of 120) and Perplexity on 100% (120 of 120). Google AI Overviews always retrieves. The glossary treats retrieval as distinct from citation, and the distinction matters here: a crawler that pays to read your page is not automatically a crawler that cites it. Getting cited is the part answer engine optimisation, defined covers.

So charging has two bills. One is money you receive. The other is the traffic and citation you may not get. Nobody has published a clean measurement of the second one.

How to make money from AI crawlers in plain terms

  • Decide whether you want cash or visibility from each crawler class. They are not the same decision.
  • Use crawl classification before you price. AI Crawl Control is the shipped product; Pay Per Crawl is the beta one.
  • Price access at the resource level, not the site level, if you can. The Monetization Gateway is designed for that.
  • Watch your referral rate after you turn pricing on. That is the honest signal, and it is measurable.

Kunzum's method is public if you want to copy the retrieval-measurement approach.

What nobody can tell you yet about earnings

There is no public payout data for Pay Per Crawl. Not per site, not per industry, not per crawler. Cloudflare has not published it, and no third party has measured it. Any post that quotes a figure is making one up.

You can see the wider x402 picture, and it is thin on the commerce side. According to TRM Labs, x402 on Base, Solana and Polygon has settled 198.9 million transactions worth $52.7 million since May 2025, of which $25.62 million screens as genuine commerce, and only 0.6% to 7.5% of that appears agentic. 99.6% of value settled in USDC. Chainalysis reports that payments of $1 or more went from 49% of value in early 2025 to 95% by early 2026, which is a sign of larger payments, not more of them.

Average ticket size stays small. Citing Artemis, CoinDesk reported around $28,000 of real daily x402 volume at an average payment near $0.20 against roughly 131,000 daily transactions. BlockEden.xyz recorded daily x402 transactions falling from about 731,000 in December 2025 to about 57,000 in February 2026, a decline over 92%.

Turn Pay Per Crawl on today and you cannot know what it will earn, because nobody has published the number.

That is the honest position. The mechanics are documented. The payouts are not.

Questions

Is Cloudflare Pay Per Crawl available for anyone to sign up for?

Not as a general setting. Cloudflare's launch post describes Pay Per Crawl as a private beta, so check your own Cloudflare dashboard for whether it is offered to your zone.

What does a crawler get when it requests a URL protected by Pay Per Crawl?

Cloudflare returns HTTP 402 instead of the asset. The 402 is a payment request, not a block page. A crawler built to read it can decide the price is acceptable and pay without a human in the loop.

Who sets the price in Pay Per Crawl and who is the merchant of record?

The publisher sets the price. Cloudflare is the merchant of record, so the payment relationship runs through Cloudflare rather than directly between the site and the crawler.

Published 2026-10-01. Written by Narender Charan, who runs Kunzum.