Project Cafecito / Espresso

Market intelligence for developers.

Espresso is an API for research, monitoring, and AI briefings. Search concrete Events and synthesized Signals, then follow the links that connect interpretation to supporting context.

Live API · REST and MCP · JSON, YAML, and TOON

ESPRESSO / INTELLIGENCE FLOW
EVENT What happened?

A concrete business or market development.

SIGNAL What could it mean?

A synthesized conclusion, implication, or outlook.

Supporting EventsEvidenceSources
Illustrative workflow; record details and available links vary.

How Espresso works

Go from a question to a traceable answer.

Events and Signals stay separate, so your application can present a development, its interpretation, and the available support without blending them together.

01

Find a development

Search Events with natural language and supported filters for the business context that matters to you.

02

Explore the signal

Inspect related Signals for synthesized implications and outlook, where available.

03

Check the support

Follow a Signal to supporting Events, then inspect available evidence and Source metadata.

Built for useful context

Structure for the question behind the headline.

Get the records your workflow needs while keeping the supporting trail close at hand.

Separate fact from interpretation

Search concrete Events and synthesized Signals as distinct records, so a briefing can show what happened alongside what it may mean.

Follow the supporting context

Move from a Signal to its supporting Events, then inspect available evidence and Source metadata before using a conclusion.

Ask focused questions

Combine natural-language search with supported filters for companies, people, products, regions, categories, and more.

Where it fits

Intelligence for the way you work.

Research briefings

Start with a development, explore related interpretation, and give readers a path back to the available evidence.

Market monitoring

Build repeatable searches around the topics and entities your team follows.

AI agents and dashboards

Bring structured Events and Signals into an application through REST or MCP.

Made for builders

Use it in your stack.

Retrieve Events and Signals through REST or MCP. Choose JSON, YAML, or TOON for the same logical payload, and use cursor pagination for longer result sets.

Explore example workflows
ACCESSREST / MCP
FORMATSJSON / YAML / TOON
RETRIEVALSearch / Filter / Traverse

Good to know

A few practical details.

How do I start?

The developer portal has the current API guide, authentication details, and reference. Check it for access information.

Is every Signal backed by the same amount of evidence?

No. Available links and record fields vary. Follow the supporting Events and Sources, and verify material information before acting on it.

Can I read Espresso without building an integration?

Yes. Espresso Publications offers human-readable analysis. The API and MCP are the integration surfaces.

Start with Espresso

Build a clearer path from development to insight.

Explore the API, its workflows, and the current documentation.

Explore the Espresso API

Espresso includes generated interpretation that may omit context or contain errors. It is not financial or other professional advice; verify consequential information against available sources.