Cloudflare launches Pay Per Use beta to monetize AI content usage

Cloudflare has launched the Pay Per Use beta, a system allowing publishers to monetize content when AI products actually use it, rather than just crawling it. This addresses the issue where AI answer engines summarize content without sending traffic, leaving publishers without revenue. The model shifts from charging for access (like Pay Per Crawl) to charging for value delivered, such as a cited excerpt or a recommendation.

How the Model Works

The process involves four key steps connecting buyers and publishers:

1. Define Paid Use: AI companies define specific uses they will pay for (e.g., returning an excerpt in search) and set a price.
2. Publisher Consent: Publishers review offers in the Cloudflare dashboard under Monetize → Pay Per Use and choose whether to accept. No technical integration is required on the publisher's side.
3. Usage Reporting: Buyers report each use via a single API, sending a JSON line with the timestamp, URL, and event ID. Reporting is self-reported but verified against enrolled publishers.
4. Settlement: Cloudflare aggregates usage, bills the buyer, and pays publishers monthly.

Benefits for Buyers and Publishers

For buyers, the model provides access to high-value, fast-changing content (news, research) behind paywalls without needing thousands of individual contracts. They are identified as verified buyers and pay only for content their product actually uses.

For publishers, the system offers transparency and control. They can see which AI companies use their content, how often, and what it earns. This data helps inform both commercial decisions (which content to monetize) and editorial decisions (what to update for agent visibility). The tool integrates with Answer Engine Optimization (AEO) to connect content discovery with revenue.

Broader Economic Infrastructure

Pay Per Use is part of Cloudflare's effort to build an economic layer for the agentic web. It complements the Monetization Gateway (also in beta), which uses the open x402 protocol to charge agents per request for APIs and tools. Both systems rely on shared foundations of identity, metering, pricing, and analytics, allowing publishers to choose between different monetization models based on their content type.