Signals
Synthesized conclusions derived from Events
Find synthesized Signals
Use when the user asks what a set of developments means, what impact is expected, or what broader conclusion Espresso has produced. Returns synthesized Signals, not raw observations or article content.
Carry a selected data[].id into Signal detail, then list supporting Events when the conclusion needs substantiation. Search Events instead when the user needs a concrete development rather than an interpretation.
from and to bound Signal created_at; tags are fuzzy text matches, while impact levels and impacted domains are exact normalized values.
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 Signal created_at lower bound (YYYY-MM-DD).
toInclusive Signal created_at upper bound (YYYY-MM-DD).
idsRestrict to Signal UUIDs (CSV).
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 synthesized Signals › Responses
Signal collection envelope
Collection pagination. Send next_cursor unchanged as the next request cursor. The response does not include a cursor echo field.
Inspect one Signal
Use after selecting a Signal from a collection. Returns its complete public fields, optional Source provenance, and a link/count for Events that support the conclusion.
Carry the Signal ID to /signals/{signal_id}/events when an answer needs concrete supporting developments. created_at is record creation time.
path Parameters
signal_idSignal 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 Signal › Responses
Signal detail envelope
Signal detail record. Collection Signal fields plus conditional links and counts.
Inspect Events supporting a Signal
Use after selecting a Signal when an agent must explain, verify, or cite the concrete developments behind its conclusion. Returns Events that support the Signal. Apply Event filters only to narrow this existing support set. This route does not perform a new semantic search and does not return unrelated Events. An empty collection means no supporting Events match the supplied filters.
path Parameters
signal_idSignal UUID (RFC 4122).
query Parameters
idsRestrict returned Events 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 returned Events to Source UUIDs (CSV).
tagsFuzzy text match against persisted Event tag labels (CSV).
fromInclusive Event created_at lower bound (YYYY-MM-DD).
toInclusive Event 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 Events supporting a Signal › Responses
Events supporting this Signal
Collection pagination. Send next_cursor unchanged as the next request cursor. The response does not include a cursor echo field.

