Recipes / Watch for regulatory action in a sector
Watch for regulatory action in a sector
/stories in hybrid mode. This page is the
operational half — what comes back, how it breaks, and what running it for real takes.
The request
GET /stories
?q=<sector> regulator investigation ruling fine consultation
&mode=hybrid
&from=<now - 14d> As a call you can paste:
curl -s -G "https://api.unzoi.com/stories" \
-H "x-api-key: $UNZOI_KEY" \
--data-urlencode "q=<sector> regulator investigation ruling fine consultation" \
--data-urlencode "mode=hybrid" \
--data-urlencode "from=<now - 14d>"
For an agent rather than a script, the same query is the list_stories
MCP tool with these as its arguments.
Parameters used here
What comes back
Clusters covering each action, typically the regulator statement plus trade and general coverage collapsed together.
Field by field: the /stories response reference.
How this goes wrong
A seven-day window and a conclusion that coverage is sparse. The publication rhythm, not the coverage, is what is sparse — this is the recipe where sampling artefacts most often get mistaken for a data problem.
Adapting it
Narrow to a specific regulator by adding its name and scoping to outlets that cover it closely, which is usually a small trade press set rather than the general press. For consultations rather than enforcement, widen the window further still — consultation periods run for weeks and coverage appears at the open and the close with nothing in between.
Running it for real
Run this weekly rather than hourly. The publication rhythm makes frequent polling wasteful, and nothing here is time-critical to the hour. Keep an eye on the outlet mix: an action covered only by the regulator's own announcement and one trade publication is at a different stage from one the general press has picked up, and that distinction usually matters more than the content of the action itself.
Related recipes
Why this approach
The case for these parameters over the obvious alternatives — and when this recipe is the wrong tool entirely — is on the recipe's page on unzoi.com. It is kept there rather than repeated here, so the argument and the operations cannot drift apart.