TL;DR
- Cloudflare moved Pay Per Use to beta on 30 September 2026: AI companies offer a price for a defined use of publisher content, publishers accept or decline, and Cloudflare pays them monthly.
- Buyers report each use as a JSON line with time, source URL and event ID; the post says usage is self-reported and Cloudflare checks that each use maps to an enrolled publisher.
- Monetization Gateway, which charges AI agents per request through the open x402 protocol, entered beta the same day.
- The post names no buyers and gives no prices, payout totals, general-availability date or eligibility rules.
Cloudflare moved Pay Per Use into beta on 30 September 2026, a system where AI companies offer a price for a specific use of a publisher's content, publishers accept or decline, and Cloudflare bills the buyer and pays the publisher monthly. The same blog post says Monetization Gateway, a separate product that charges AI agents per request using the open x402 protocol, entered beta the same day. What is new compared with RA's 19 September 2026 payment-models post is the beta launch itself and the mechanics Cloudflare published with it; that earlier post compared Pay Per Crawl with Google's and Microsoft's schemes and noted that Cloudflare was reshaping Pay Per Crawl into Pay Per Use.
What Cloudflare announced on 30 September 2026
The Cloudflare blog post, titled "Pay Per Use: when AI uses your work, you should get paid" and written by four Cloudflare authors, says Pay Per Use is now in beta. It adds that Cloudflare outlined its plan for the product in July 2026 and has since worked with buyers and content owners to build it. Buyers in this setup are AI companies; publishers are the content owners who decide whether to accept an offer.
The central argument in the post is that AI products fetch far more than they use. Cloudflare gives the example of a search engine that indexes pages it never shows. Charging for every crawl, the post says, makes the buyer pay before it knows what it needs, and many buyers will not. Paying for use ties the price to the value the buyer receives. In the post's words, Pay Per Crawl, which Cloudflare launched in 2025, charges for access, while Pay Per Use pays for what happens next.
The post also states that publishers can choose the model that suits them, so the two products are presented as options, not as a replacement of one by the other.
How Pay Per Use works, step by step
Cloudflare describes four steps in its 30 September post, and each one carries a detail that matters for anyone deciding whether to take part.
Step 1: the buyer defines a paid use
Each AI company sets up its program with Cloudflare. It identifies its crawler, defines the use it will pay for, sets a price and connects a payment account. The post gives two sample offers: a search service that pays when it returns an excerpt from an enrolled page to a customer, and a shopping agent that pays when an enrolled review shapes a recommendation. Under the second example, the post notes, payment follows use even if the shopper never reads the review. The buyer proposes the definition of the paid use; Cloudflare supplies the reporting and payment infrastructure.
Step 2: the publisher chooses
Publishers review offers in the Cloudflare dashboard under Monetize, then Pay Per Use. Each offer shows the AI company, the use it pays for and the offer price. Publishers decide whether to accept and can stop participating if an arrangement no longer works. The post says there is no origin change and no separate technical integration with each AI company. It also says each program's terms define what the AI company may do with the content, including any restrictions on training.
Step 3: the buyer reports each use
The buyer fetches the list of domains that accepted its offer and reports each use as one line of JSON containing when it happened, the URL the content came from and an event ID. The post is explicit that usage is self-reported: the program terms require complete reporting, and Cloudflare checks that each reported use maps to an enrolled publisher. The post does not describe any audit of whether a reported use actually happened or whether unreported uses exist.
Step 4: Cloudflare settles both sides
Cloudflare aggregates the reported uses, charges the buyer and pays publishers monthly through their connected payment account. Buyers get one integration, and publishers get one place to see offers and earnings.
Pay Per Crawl, Pay Per Use and Monetization Gateway compared
The 30 September post puts three Cloudflare monetization options next to each other, and the table below restates only what that post says about each one.
| Product | What is charged | How it is measured |
|---|---|---|
| Pay Per Crawl (launched 2025) | Access to content | Charged when content is fetched, before the buyer knows what it will use |
| Pay Per Use (beta since 30 Sep 2026) | A buyer-defined use of content, such as a cited answer | Buyer self-reports each use via API; Cloudflare bills monthly |
| Monetization Gateway (beta since 30 Sep 2026) | Each request to an API, tool or dataset | Per request, using the open x402 protocol |
The post says the last two run on the same foundations: identity, metering, pricing and analytics. It frames the split by content type. High-value content, it says, needs a trusted network of verified buyers who report how they use it, and that is Pay Per Use. APIs, tools and data are often different because every request is the use, and for those Monetization Gateway lets sellers charge agents per request.
What the dashboard shows publishers
Cloudflare says publishers can already see how often each AI company uses their content and what it earned, by domain and over time. The dashboard described in the post shows estimated earnings and reported uses over time, broken down by buyer and domain. The post contrasts this with Business Insights, which it says already shows which crawlers visit and what they take; Pay Per Use adds whether that content was actually used, how often and what it earned.
Cloudflare also says it is working with AI companies to report more context about each use, such as the keywords that led to a citation, the topic of the request or the product the use powered, with no personal data exchanged. That is described as a next step, not a current feature. The post links the idea to Cloudflare's Answer Engine Optimization tool, which it says shows how assistants answer questions about a publisher's work, and says the combination connects how content is found, how it is used and what it pays.
What the post leaves open
A beta announcement is not a market, and the Cloudflare post leaves several questions unanswered. These are gaps in the source, not findings about the product.
- It names no buyers. The post does not say which AI companies have joined or intend to join.
- It states no prices. The only price mechanics described are that each buyer sets one and each publisher accepts or declines it.
- It gives no payout totals and no figure for how much any publisher has earned.
- It sets no general-availability date. The beta section says Cloudflare is working directly with each buyer and with the publishers who opt in, and that the question is whether both sides want to keep going.
- It does not specify the settlement currency, price limits or eligibility rules for Monetization Gateway, and it gives no sign-up conditions for Pay Per Use.
- It does not say whether Thai publishers or Thai-language content can take part.
The post also lists features it wants later: letting new buyers onboard with their own payment models, and giving publishers one place to accept or decline offers, counter on price and price content differently by use. Its own example is that last week's reporting may be worth more to an AI product than a ten-year-old archive page. These are stated intentions for after the beta, not available controls.
What this means for Thai marketers
The following is RA's analysis, not something Cloudflare said about Thailand; the post makes no Thai-specific statement. The practical point for most Thai brands is that "block or allow" is becoming a third option, "allow on terms". A Thai publisher or a brand with a large content library that AI products reuse may eventually have a way to be paid per use, but the post gives no timeline and no buyer list, so there is nothing to budget against today.
For a brand whose goal is to be named in AI answers, a payment mechanism is not the point. Brands that want visibility in AI search generally want the content read and cited, and a program that pays for each cited answer does not change that goal. What it changes is the reporting: a publisher enrolled in Pay Per Use would see, per buyer and per domain, how often content was reported as used. That would be a more specific view of AI use than a crawl count alone, which is the contrast the post itself draws with Business Insights, and it is why the program is worth watching even without any revenue expectation. Teams working on generative engine optimization can treat the reported-use data as a possible future input for judging which pages AI products actually draw on.
Two cautions apply. First, self-reported usage means the numbers depend on buyer honesty and on the program terms the post says require complete reporting. Second, accepting an offer changes what an AI company may do with a site's content, and the post says each program's terms cover training restrictions, so legal and editorial teams should read those terms before a site accepts anything.
A short checklist for a team that owns a content library: confirm which AI crawlers already reach the site by reading server logs; decide in advance whether the site's goal is payment, citation or protection; and if Cloudflare is already the site's CDN, watch the Monetize section of the dashboard for offers rather than assuming any will arrive. If the site is not on Cloudflare, nothing in the post suggests it can take part. RA's AI SEO service covers the visibility side of that decision.
Frequently asked questions
What is Cloudflare Pay Per Use?
Cloudflare Pay Per Use is a beta program, announced as beta on 30 September 2026, in which an AI company offers a price for a defined use of a publisher's content and the publisher accepts or declines. The buyer reports each use through an API, and Cloudflare bills the buyer and pays the publisher monthly. The post presents it as paying for use, not for crawling.
How is Pay Per Use different from Pay Per Crawl?
Pay Per Crawl charges for access, while Pay Per Use pays when content is actually used, for example in a cited answer. Cloudflare launched Pay Per Crawl in 2025 and says publishers can choose the model that suits them. The reporting also differs: Pay Per Use relies on usage that buyers report themselves.
What is Monetization Gateway?
Monetization Gateway is a separate Cloudflare product, also in beta as of 30 September 2026, that lets sellers charge AI agents per request using the open x402 protocol. The post positions it for APIs, tools and data, where each request is itself the use. It runs on the same identity, metering, pricing and analytics foundations as Pay Per Use.
Can a Thai publisher join the Pay Per Use beta?
The source does not say. The Cloudflare post gives no eligibility rules, no country restrictions and no sign-up process, and it names no buyers, so a Thai publisher would need to check the Monetize section of its own Cloudflare dashboard. Treat any claim about regional availability as unconfirmed until Cloudflare states it.
How much can publishers earn?
The source does not say. It gives no prices, no payout totals and no earnings examples; it only describes a dashboard that shows estimated earnings and reported uses by buyer and domain. Any revenue forecast at this stage would be invention.
If your team is deciding how AI products should be allowed to use your content, RA's generative engine optimization work starts from that visibility question and can help you set a position before any payment program reaches your site.
