Events
Concrete Event intelligence records and evidence relationships
Find concrete Events
Use when the user asks what happened to a company, person, product, region, or topic. Returns concrete Event records, not article bodies and not synthesized conclusions.
Carry a selected data[].id into Event detail, evidence, or related-Signals routes. Use tags for fuzzy concepts; use structured filters for exact normalized values. categories is not an alias for event_types.
Search Signals instead when the user asks for meaning, implication, or outlook. from and to bound record created_at, not occurrence or publication time.
query Parameters
qOptional natural-language semantic query. Max 1024 characters.
score_thresholdMinimum semantic similarity threshold for q. 0.0 is broad and 1.0 is strict. Default 0.5.
fromInclusive created_at lower bound (YYYY-MM-DD).
toInclusive created_at upper bound (YYYY-MM-DD).
idsRestrict to Event UUIDs (CSV).
event_typesExact Event type names in snake_case (CSV), for example policy_change,market_entry.
categoriesExact category names in snake_case (CSV), for example regulation,technology. This is separate from event_types.
entitiesExact entity names in snake_case, matched against company or people names (CSV), for example microsoft,nvidia.
impact_levelsExact impact-level names (CSV), for example high,medium.
companiesExact company names in snake_case (CSV), for example microsoft,nvidia.
peopleExact person names in snake_case (CSV), for example sam_altman,elon_musk.
productsExact product names in snake_case (CSV), for example windows,geforce.
regionsExact region names in snake_case (CSV), for example north_america,europe.
source_idsRestrict to direct Event source UUIDs (CSV).
tagsFuzzy text match against persisted tag labels (CSV).
response_typeResponse serialization: JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients. JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients.
limitMaximum records per page. Default 20, max 100.
cursorOpaque continuation token. Send pagination.next_cursor from a previous response unchanged as cursor; never construct or decode it.
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Find concrete Events › Responses
Event collection envelope
Collection pagination. Send next_cursor unchanged as the next request cursor. The response does not include a cursor echo field.
Inspect one Event
Use after selecting an Event from a collection. Returns its complete public view, optional Source provenance, and links/counts for available evidence and related Signals.
Carry the Event ID to /events/{event_id}/evidence for supporting context or source coverage, or to /events/{event_id}/signals for associated higher-level conclusions. created_at is record creation time, not Event occurrence time.
path Parameters
event_idEvent UUID (RFC 4122).
query Parameters
response_typeResponse serialization: JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients. JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients.
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Inspect one Event › Responses
Event detail envelope
Event detail record. Collection Event fields plus conditional links and counts.
Inspect evidence for an Event
Use after selecting an Event when the user needs supporting context, available source coverage, or traceability. Returns directly related evidence records with identity, creation time, tags, Source IDs, and available URLs. This is not an article-body endpoint, a story-clustering endpoint, or a complete record-history export. An empty collection means no evidence records are available for this Event under the supplied filters.
path Parameters
event_idEvent UUID (RFC 4122).
query Parameters
idsRestrict returned evidence records to Event UUIDs (CSV).
source_idsRestrict direct evidence records to Source UUIDs (CSV).
fromInclusive evidence created_at lower bound (YYYY-MM-DD).
toInclusive evidence created_at upper bound (YYYY-MM-DD).
response_typeResponse serialization: JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients. JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients.
limitMaximum records per page. Default 20, max 100.
cursorOpaque continuation token. Send pagination.next_cursor from a previous response unchanged as cursor; never construct or decode it.
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Inspect evidence for an Event › Responses
Event evidence collection envelope
Collection pagination. Send next_cursor unchanged as the next request cursor. The response does not include a cursor echo field.
Find Signals connected to an Event
Use after selecting an Event to find higher-level conclusions associated with that development. Returns Signal records that can be inspected individually or followed to their supporting Events.
An empty collection means Espresso has no available Signal connected to this Event; it does not invalidate the Event. This route narrows associated Signals; use /signals for a new Signal search.
path Parameters
event_idEvent UUID (RFC 4122).
query Parameters
idsRestrict returned Signals to Signal UUIDs (CSV).
fromInclusive Signal created_at lower bound (YYYY-MM-DD).
toInclusive Signal created_at upper bound (YYYY-MM-DD).
impact_levelsExact impact-level names (CSV), for example high,medium.
impacted_domainsExact impacted-domain names in snake_case (CSV), for example public_health,climate.
tagsFuzzy text match against persisted Signal tag labels (CSV).
response_typeResponse serialization: JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients. JSON is canonical; YAML and TOON are token-optimized for MCP and AI-agent clients.
limitMaximum records per page. Default 20, max 100.
cursorOpaque continuation token. Send pagination.next_cursor from a previous response unchanged as cursor; never construct or decode it.
Headers
AuthorizationThe Authorization header is used to authenticate with the API using your API key. Value is of the format Bearer YOUR_KEY_HERE.
Find Signals connected to an Event › Responses
Signals derived from this Event
Collection pagination. Send next_cursor unchanged as the next request cursor. The response does not include a cursor echo field.

