If your site runs through Cloudflare, Cloudflare can charge an AI crawler (a program that fetches pages in bulk) for each page it takes, and pay you. FORA lets you set terms and a price for each resource, sold through the Exchanges you choose. Each sale leaves a signed record of what was bought, and on what terms.
Updated
The facts a revenue team and an engineering lead act on. Cloudflare's cells describe Pay Per Crawl, and Pay Per Use where it differs.
| Cloudflare | FORA | |
|---|---|---|
| Money | ||
| Who pays you, and when | Cloudflare, as merchant of record, monthly, to a new Stripe Connect account, after settlement periods and payout thresholds [1, 2]. | Your Exchange operator, under its own terms. See About FORA. |
| Fees | Not public. Cloudflare's docs, posts and terms state no fee. | No Exchange fee at FORA's publisher console, beyond the payment system's. See About FORA. |
| What you see | Which crawlers visit and how often they're charged. Your earnings balance isn't in the dashboard [3]. | Each sale with its usage-report status, and daily income with a CSV download, in your operator's publisher console [33]. |
| Contract | Pay Per Crawl's program terms: not public. Pay Per Use: each program's terms say what the buyer may do [4]. No dispute process documented. | Your agreement with your Exchange operator. Your terms go into each offer the Exchange signs [34]. Disputes: see About FORA. |
| Status | Pay Per Crawl Closed beta, charging listed under Enterprise plans with Bot Management [1, 5]. Pay Per Use Beta [4]. No AI company named as paying through Pay Per Crawl. | Live See About FORA. |
| Your stack | ||
| DNS | Cloudflare's nameservers, with DNSSEC off first, or your own DNS provider on Business or Enterprise [6, 7, 8]. Every web hostname routed through Cloudflare [9]. | No record to add [33]. |
| CDN | Cloudflare only [6]. | A drop-in edge function. The rest depends on your own setup; FORA adds to what you run rather than replacing it. |
| Firewall and bot shield | Your rules run first, so a crawler they block is never offered a price [10]. Turn off Block AI Bots to join [11]. | Your WAF and bot product run first. Let signed requests and your two files through them; FORA's guide gives two setups [35]. |
| Your site and CMS | No change for one price. A price per page needs a response header from your origin or a Worker [12]. | One file, fora.json, naming your Exchanges, and a sitemap the operator imports your pages from [33]. |
| Search traffic | Only crawlers you set to Charge pay. Cloudflare warns that charging a search crawler may hurt your SEO [13]. | Googlebot, Bingbot and Applebot always pass [35]. See Search traffic, below. |
| Upkeep | Cloudflare keeps the list of crawlers you can charge [14]. Logpush can't fill in the past, and logs are lost while a job fails [15]. | Change your Exchanges by editing your discovery file, with nothing to redeploy [33]. |
| Leaving | The docs describe no step to turn Pay Per Crawl off, close its Stripe account or take a final payout. | Delete the edge function from your CDN. |
Pay Per Crawl charges a crawler one price per page, and Cloudflare collects and pays out. In Pay Per Use, an AI company proposes a price for a use, and you accept or decline. Both are in beta. Pay Per Crawl needs your site's traffic to run through Cloudflare.
You set the uses, buyers, caps and price for each resource, and can offer one article on several terms. An AI agent (software that acts for a user, one task at a time) buys under an offer your Exchange signs. Pay Per Crawl needs no Exchange of yours, because Cloudflare is one.
Cloudflare's plan table lists charging under Enterprise plans with Bot Management. You need a new Stripe account, and your balance isn't in the dashboard. Cloudflare names no AI company paying through it.
The agent finds the Exchange that sells your content: from your site, or through a Broker's search across catalogs.
It asks for the content and gets signed offers: the price, the permitted uses, the obligations.
It commits to one offer, pays through the Exchange and gets a signed receipt.
It fetches the file through a short-lived link bound to its identity.
It reports what it used, when the offer asks for a report.
If the file is wrong or never arrives, it opens a dispute backed by signed evidence.
In both programs, Cloudflare charges the buyer and pays you monthly. They differ in who sets the price.

In Pay Per Crawl (closed beta) you set one price for every crawler set to Charge, Cloudflare quotes it with HTTP 402, charges each successful fetch and pays you monthly. Pay Per Use (beta) reverses who sets the price: the AI company sets a price for a use it defines, you accept or decline, the buyer reports its own uses, and Cloudflare charges the buyer and pays you monthly.
Pay Per Crawl, in six steps:
Pay Per Use reverses who sets the price (Pay Per Use, published 2026-09-30). An AI company "defines the use it will pay for and sets a price", such as returning an excerpt of your page to a customer. You accept offers in the dashboard, with "no origin change". "Usage is self-reported": the buyer reports its own uses, and Cloudflare charges the buyer and pays you monthly. Its reason for the program: "AI products fetch far more than they use".
Pay per crawl is currently in closed beta.
Cloudflare names no AI company paying through Pay Per Crawl in any doc, post or press release. Press Gazette reported on 2026-08-17 that it "remains in closed beta testing" (Press Gazette). The publishers Cloudflare listed in 2025 were named "in support", not as participants. Participant counts and payout totals are not published.
For Pay Per Use, Cloudflare says it is "running experiments" with Ceramic.ai and You.com (Making AI search smarter, published 2026-07-01).
Pay Per Crawl needs your traffic routed through Cloudflare. Your other Cloudflare rules decide which crawlers it ever sees, and only crawlers on Cloudflare's list can be charged.

A crawler meets your DNS and proxy first (a hostname left unproxied never meets Pay Per Crawl), then your firewall rules and bot tools (a crawler they block is never offered a price), then Pay Per Crawl, where you set each listed crawler to Charge, Allow or Block; HTML isn't cached by default, so each crawl normally reaches your origin. The crawler gets the page if allowed, a 403 (refused) or a 402 (pay first) with your own message if blocked, a 402 (pay first) with the price if it is charged without an agreement, and the page, charged, if it agreed.
fora.json file, the edge function and an Exchange.Cloudflare runs one company's exchange inside its network; FORA is a protocol that any company can run an Exchange on. On your site they sell the same page, side by side, and they work together on bot detection and hosting. The price and money rows compare different things: one number per fetch against a menu of terms, and a company that moves money against a protocol that doesn't.
| The question | Cloudflare | FORA |
|---|---|---|
| How do you say what's for sale? | Dashboard settings: allow, charge or block per listed crawler, one price, free paths [12, 13, 16]. Preferences go in robots.txt as Content Signals, a line that states a preference with no price [30]. Cloudflare's docs describe no license in the 402. | A file on your site names your Exchanges [34]. Each resource can carry several terms, up to 32: uses, buyers, places, caps, duties and a price [36]. |
| How does a buyer find your content? | A registered crawler asks Cloudflare for the domains that charge it, finds pages itself, and gets each page's price from a 402 [18, 20]. Pay Per Use: the domains that accepted its offer [4]. | An agent asks your Exchange, or a Broker, which returns the signed offers whole (how a Broker orders offers) [37]. |
| Who is the buyer, provably? | A Web Bot Auth signature in an older draft's form, which deployed crawlers still send, plus a reviewed registration [18, 24, 40]. On the free plan, the user agent [22]. | A Web Bot Auth signature in the form of the working group's first draft (-00), checked against a key on the buyer's domain [38]. |
| What lets a given use happen? | Cloudflare's edge, per request: a verified crawler set to Charge, with a signed price [18]. Use limits sit in robots.txt, or in each Pay Per Use program's terms [3, 4]. | An offer the Exchange signs and the agent accepts and signs, then a signed link that expires, checked at your CDN [34]. |
| Who sets the price, in what unit? | You: one price per fetch for every charged crawler, or a price per page [12, 16]. Pay Per Use: the buyer sets a price per use; you accept or decline [4]. | You, per term: free, per unit (a fetch, an access, a token) or flat. One article can be free for research and paid for commercial use. No revenue-share price [36]. |
| How does money move? | Cloudflare charges the buyer through Stripe and pays you monthly [2]. Its fee isn't published. | Outside the protocol. See About FORA. |
| What do you see? | Which crawlers visit, how often they're charged, robots.txt violations. "Your accrued earnings balance is not currently visible in the dashboard." (Monitor activity) | A signed record of each sale, with its usage-report status, in the publisher console your Exchange operator runs [34]. No protocol call returns your sales. |
| What if the numbers are wrong? | No dispute process is documented. Pay Per Use reports are the buyer's own; Cloudflare checks each names an enrolled site [4]. | Defined in the protocol, handled under your operator's rules. See About FORA. |
FORA pins Web Bot Auth -00; the working group published -01 on 2026-10-29 [38, 40].
Settling a FORA sale through Pay Per Crawl. Pay Per Crawl charges when a crawler fetches a page. Its docs describe no way to bill an amount for a sale made elsewhere.
A Cloudflare price a FORA agent can verify. Cloudflare's docs describe no signed price or receipt. The crawler gets a header that states the amount charged.
fora.json, set terms per resource, and run FORA's edge on the paths you license.Sources are checked on the date of publication.
FORA is an open protocol and free, open-source software. Sell through any FORA marketplace, several of them, or your own: you set terms and a price per resource, and each Exchange signs your offers.