Espresso API & MCP

MCP-ready business intelligence over curated "sips" for agents, dashboards, and automated research workflows. A sip is one unit of intelligence. event records describe observed business or market developments. signal records synthesize higher-level implications from related events and actions. action records are lower-level source facts used by the ingestion pipeline. Agent workflow: (1) listTags to discover filter vocabulary; (2) searchEvents for time-ordered developments; (3) searchSignals for synthesized implications; (4) getRelatedSips to follow same_as duplicates or derived_from intelligence chains. Conventions: Auth is optional at the backend but API-key protected through the gateway. Pagination uses limit default 16 max 128 and offset default 0. Empty result sets return HTTP 204, not an error. All sip IDs are UUID strings such as 339366bc-464d-582f-8132-6875ccc814d2. Response formats: use response_type=json for structured application data. Use response_type=text for MCP/LLM context; it returns the same underlying records as compact field-per-line plain text with lower token overhead.