Events

Returns event-kind sips. Searches without q are sorted by created descending; semantic searches with q are ranked by cosine distance, most similar first. When to use: retrieve concrete developments, incidents, company actions, policy changes, market moves, or other observed business events before moving to higher-level signals. Search modes: use ids for exact UUID lookup, tags for inclusive-AND tag filtering, q + acc for semantic search, and from to set the oldest creation date. These filters can be combined. Default time window: when from is omitted, the service uses its default recent window, currently about the last 7 days. Response shape: JSON responses are flattened digest objects with id and reported added by the router. Stable fields include briefing, event_type, actions, people, regions, cross_domain_impacts, future_outlook, impact_level, and tags; additional pipeline-specific keys may appear. Agent format: use response_type=text for compact field-per-line records when feeding an LLM or MCP client. Use JSON when the caller needs structured parsing.