API reference

Context Graph Cascade API

Cascade walks the graph up from a company to the macro and policy drivers that flow through its sector down to it, and out to the peers that share those drivers.

What it returns

The response returns sectors, a drivers list (the name's own exposures plus its sector's macro and policy factors), impact_paths read top-down as driver to sector to company, shared_with_peers, a narrative, a trust block, and a source indicator.

Drivers come from the name's exposed_to edges merged with a per-sector macro map covering Technology, Energy, Financials, Consumer, Healthcare, and Industrials.

When to use it

Use Cascade to trace why a name moves: which top-down forces drive its sector and which peers share that exposure. It is the connected view a generic data feed or single-ticker LLM wrapper cannot reconstruct.

When a name is not yet mapped to sector-level drivers it says so and points you to seeding its sector or connecting a live source.

Notes and honesty

Cascade reads the Knowledge Graph, so it inherits the same seed-versus-live honesty: offline it uses curated seed relationships and a curated macro map. It describes structural relationships, not a buy or sell view, and records nothing.

curl -s 'https://api.lyramindos.com/v1/graph/cascade?symbol=XOM' -H 'x-api-key: YOUR_KEY'
GET /v1/graph/cascade?symbol=

Questions

How are drivers determined?

They combine the name's own exposed_to edges with a curated per-sector macro map (for example Energy maps to crude oil price, OPEC supply policy, and refining margins). The result is deduplicated and read top-down.

What if a name has no sector mapped?

The response says the name is not yet mapped to sector-level drivers and suggests seeding its sector or connecting a live source, rather than guessing.

Is this a market prediction?

No. It maps structural relationships between macro drivers, sectors, and companies. It is descriptive context only, never advice or a prediction.

Related

See the live demo →Request access