Cloudflare Launches Pay Per Use Beta to Monetize Downstream AI Content Consumption

Cloudflare Launches Pay Per Use Beta to Monetize Downstream AI Content Consumption Cloudflare has introduced Pay Per Use in beta, a marketplace and payment infrastructure enabling publishers to charge AI companies when their content is actually used downstream, rather than charging simply for web crawling. AI companies define specific use cases, set their offer prices, and connect payment accounts, while publishers can accept or decline terms in their Cloudflare dashboard without technical integrations. Pay Per Use distinguishes itself from Pay Per Crawl by charging only when content powers a downstream output, such as search citations, agent reports, or product recommendations. Buyers self-report downstream content consumption via a single-line JSON API, which Cloudflare aggregates to manage monthly billing and publisher disbursements. Alongside Pay Per Use, Cloudflare launched a Monetization Gateway beta using the x402 protocol to charge AI agents per request for API, tool, and data access. Mechanics of Pay Per Use Under the Pay Per Use model, AI companies register as Verified bots, define the specific downstream use of content they will pay for (such as excerpts in search or citations in shopping recommendations), set an offer price, and provide payment details. Publishers review and accept or decline these offers directly within the Cloudflare dashboard without needing individual integration contracts or origin server changes. Program terms also define permitted actions and training restrictions. Usage Reporting and Settlement Unlike the Pay Per Crawl model introduced in 2025 that charges for initial site access, Pay Per Use bills only when fetched content is actively utilized. Participating buyers identify accepted domains and self-report each consumption event through a JSON API detailing the timestamp, source URL, and event ID. Cloudflare verifies that the reported uses align with enrolled publishers, aggregates the data, bills the buyer, and issues monthly disbursements to publishers. Analytics and Complementary Monetization Tools Publishers can monitor usage frequency and earnings alongside bot traffic data from Cloudflare's Business Insights and Answer Engine Optimization tools, helping guide commercial and editorial decisions. Future plans include reporting non-personal context such as query topics and keywords. For request-based resources like APIs and structured datasets where every access constitutes a use, Cloudflare simultaneously launched the Monetization Gateway beta powered by the x402 protocol.

Cloudflare推出Pay Per Use测试版：让出版商从AI的实际使用中获得收益 Cloudflare宣布推出Pay Per Use（按使用付费）测试版。该机制使AI公司能够为其在产品中实际使用的内容向出版商付费，出版商无需逐一谈判即可按需授权并获取持续回报。 Pay Per Use针对下游实际使用计费，弥补了传统按抓取收费（Pay Per Crawl）无法衡量实际价值的不足。 AI买家自行设定使用场景与出价，出版商在控制台自主决定是否接纳方案及训练限制。 买家通过单一API上报使用记录，Cloudflare负责汇总对账、向买家收费并按月发放给出版商。 应对AI摘要带来的流量流失 AI回答引擎直接生成摘要导致用户不再点击原始网页，中小出版商也难以同各家AI公司逐一达成授权协议。与2025年推出的按抓取计费（Pay Per Crawl）不同，Pay Per Use将费用直接与AI实际使用产生的价值挂钩，出版商可自主选择契合自身的内容变现模式。 运作流程与自动化结算 AI公司需定义其付费的使用方式（如搜索引用或生成推荐）并设定单价。出版商在Cloudflare控制台中即可查看并决定接受或退出该方案，并保留对模型训练等下游用途的限制。买家获取已接受方案的域名列表后，通过API以JSON格式自报使用事件，Cloudflare核验后按月向买家收费并结算给出版商。 数据洞察与配套工具体系 出版商可通过控制台追踪内容在各AI产品中的使用频度与收益，结合AEO工具指导商业与采编决策。此外，针对高价值内容采用Pay Per Use模式的同时，Cloudflare还推出了基于开放x402协议的Monetization Gateway测试版，方便数据和API服务按请求向AI代理计费。

AI answer engines read a publisher’s page and hand the reader a summary, so the visit, and the revenue that would come with it, never happens. Most publishers will never sign a licensing deal with the companies that use their work in AI products, and no company can negotiate with millions of sites. The web needs a way to say [“yes, if you pay.”](https://blog.cloudflare.com/agentic-web/) Pay Per Use is one way to say it, and it's now in beta. In July, we outlined our plan for Pay Per Use. Since then, we’ve been working with buyers and content owners to bring it to life. The gist: A buyer offers a price for a specific use of your content. You choose whether to accept. The buyer reports each use, and Cloudflare bills the buyer and pays you. Publishers track usage and earnings in the Cloudflare dashboard. Buyers report usage through a single API. AI products fetch far more than they use. A search engine indexes pages it never shows. Charging for every crawl makes the buyer pay before it knows what it needs, and many buyers won't. Paying for use ties the price to the value the buyer actually gets, which we hope brings more buyers to the table and more money to publishers. [Pay Per Crawl](https://blog.cloudflare.com/introducing-pay-per-crawl/), which we launched in 2025, charges for access. Pay Per Use pays for what happens next. Publishers can choose the model that suits them. For buyers, the case is just as simple. Some of the content your product needs is behind a block or a paywall today, and it’s the content that changes fastest: news, research, specialist trade publications. Pay Per Use lets buyers make an offer. You pay only for the content your product actually uses, you’re identified to every publisher as a verified buyer, and one API connects you to every site that says yes. You won’t need thousands of integrations or individually-negotiated contracts. Each AI company defines the use it will pay for and sets a price. Publishers decide which offers to accept, and then can see how often their content is used and what it has earned. Cloudflare handles enrollment, usage records, billing, and payment. Pay Per Use lets publishers make their content available to identified AI companies on terms that turn downstream use into revenue. Publishers choose which programs to join and retain control over crawler access and downstream uses. AI companies identify their crawling activity using [Verified bots](https://developers.cloudflare.com/bots/concepts/bot/verified-bots/) and, when permitted by the publisher’s controls, can access and index content owned by the publisher. That content can later power many experiences: a cited answer in AI search, a passage quoted in a research agent's report, a product review weighed by a shopping agent, or a recipe adapted by a cooking assistant. Let’s show how it works! 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. Consider two possible offers. A search service could pay when it returns an excerpt from an enrolled page to a customer. A shopping agent could pay when an enrolled review shapes a recommendation. Under the second offer, payment follows use even if the shopper never reads the review. The same article can create value in different products and publishers can accept different payment offers for different uses. The buyer proposes the definition of the use being paid for; Cloudflare provides the reporting and payment infrastructure. Publishers review offers in the Cloudflare dashboard, under Monetize → Pay Per Use: it will show the AI company, the use it pays for, and its offer price. Publishers decide whether to accept, and can stop participating if an arrangement no longer works for them. There is no origin change or technical integration with each AI company. Each program’s terms also define what the AI company may do with the content, including any restrictions on training. The buyer fetches the list of domains that have accepted its offer, then reports each use as one line of JSON: when it happened, the URL the content came from, and an event ID. Usage is self-reported: the program terms require complete reporting, and Cloudflare checks that each reported use maps to an enrolled publisher. We aggregate reported uses, charge the buyer, and pay publishers monthly through their connected payment account. Buyers get one integration. Publishers get one place to see offers and earnings. Today, publishers see how often each AI company uses their content and what it has earned, by domain and over time. [Business Insights](https://developers.cloudflare.com/bots/business-insights/) already shows which crawlers visit and what they take. Pay Per Use shows what happens next: whether that content was actually used, how often, and what it earned. Next, we’re working with AI companies to report to publishers more context about each use, such as the keywords that led to the citation, the topic of the request, or the product it powered, with no personal data being exchanged. Our [Answer Engine Optimization (AEO)](https://blog.cloudflare.com/aeo/) tool shows how assistants answer questions about your work. Pay Per Use shows what buyers report using, and what that use earned. Together, they connect how your content is found, how it's used, and what it pays. That helps with two kinds of decisions. Commercial ones: which content earns, which uses are worth it, and whether to keep participating. And editorial ones: what to cover, what to update, and what to make easier for agents to find. During the beta, we’re working directly with each buyer and with the publishers who opt in. The question is simple: do both sides want to keep going? Buyers need content that improves their products at a price that works. Publishers need a return that makes participation worthwhile, reporting they can trust, and payments that arrive on time. Over time, we want new buyers to onboard with their own products and payment models, without rebuilding enrollment, reporting, and settlement for each publisher. For publishers, that means one place to accept or decline offers, counter on price, and price content differently by use. Last week’s reporting may be worth more to an AI product than a ten-year-old archive page, and you should be able to charge for that. The beta will help us determine how to make those choices simple and practical at scale. Content should be able to reach new audiences and generate sustainable revenue, even when it becomes part of someone else's product: a cited search result, a shopping recommendation, an agent's report. Pay Per Use turns those uses into a commercial relationship. A buyer makes an offer, a publisher chooses whether to accept, and the use of valuable content leads to payments and records of what happened. Not everything should be sold the same way. High-value content needs a trusted network of verified buyers who report how they use it, and that's Pay Per Use. APIs, tools, and data are frequently different, because every request is the use. For those, [Monetization Gateway](https://blog.cloudflare.com/monetization-gateway-beta) (also in beta as of today) lets sellers charge agents per request, using the open x402 protocol. The two run on the same foundations: identity, metering, pricing, and analytics. Publishers shouldn't have to choose between blocking every agent and giving their work away. Pay Per Use gives them a way to say yes, on clear terms, with an account of what happened.