This belongs in a compact slot, not the lead, because there is no same-day API change. The useful public decision is narrower: builders can make agents find the dataset record, resources, producer, and reuse context before summarizing or downloading government data.
Signal
The api.gouv.fr catalogue file for API catalogue des donnees ouvertes - data.gouv.fr links the public Swagger definition at https://www.data.gouv.fr/api/1/swagger.json and says the API lets users consult dataset metadata, manage dataset records, and work with producer organizations and reuses.
Try It
Copy-paste agent instruction: Search the data.gouv.fr API for the dataset topic I give you. Return the best dataset title, producer, resource URLs, license or access caveat if present, and one reason a human should verify the source before using the data.
Creative Example
Ask an agent planning a local climate dashboard to search for public datasets on heat islands, then make it list the dataset record and resources before it writes analysis code.
Caveat
Catalogue metadata is intake, not truth. Test caveat: the agent still has to inspect the actual resource file, update date, license, and producer page. What to watch: whether API docs add more agent-friendly examples for ambiguous dataset searches.