Fusion Response
Fields of the cyber-market fusion view, its sources, exposure paths, provenance, adjacencies, and read budgets
GET /api/v2/entities/{entityId}/fusion and the in-app Cyber-market exposure panel return the
same view for an organization or vendor entity.
Parameters
| Parameter | Default | Range | Meaning |
|---|---|---|---|
windowDays | 90 | 1–365 | Days of history ending at request time |
adjacencyDays | 7 | 1–90 | How long after a cyber event a market event counts as adjacent |
Response fields
| Field | Meaning |
|---|---|
entity | The resolved company (after catalog merge redirects) |
window | start, end, and adjacencyDays actually used |
counterparties | Up to 12 parties on the exposure path, with relation, provenance, and, for ledger ties, confidence and verification |
identifiers | Live designations of ledger subjects anchored to the company |
topics | Workspace topics whose subject is the company or a counterparty, with the path relation |
timeline | Up to 200 dated events in the window, newest first |
undated | Events without a source time, never placed at a guessed date |
summaries | Per domain: event count, highest severity, latest event time |
adjacencies | Up to 50 cyber → market pairs within adjacencyDays, same-path pairs first |
coverage | truncated and plain-language notes on read budgets and source limits |
Exposure paths
| Relation | From a catalog relation | From a ledger claim |
|---|---|---|
supplier | The party supplies the company | The party's subject supplies the company's subject |
customer | The company supplies the party | The company's subject supplies the party's subject |
parent | The company is subsidiary_of the party | The company's subject is subsidiary-of the party's subject |
subsidiary | The party is subsidiary_of the company | The party's subject is subsidiary-of the company's subject |
operated-system | The company operates or uses a software, API service, or model entity | The company's subject operates a system subject |
A ledger tie wins over a catalog tie to the same entity because it carries evidence and a verification state.
Catalog exposure paths use the resolved relation projection. Changing windowDays filters event
times; it does not reconstruct historical catalog relations or what Y2 knew at an earlier date.
Ledger exposure paths use claims valid at window.end.
Event sources
| Domain | Sources |
|---|---|
cyber | CVEs that affect, and actors that target, the company or a path party; readable cyber signals; cyber incidents |
market | Readable market signals; the workspace's financial facts at their information date; prediction markets about a path party; economic incidents |
supply_chain | Ledger supply and ownership ties at their valid_from; readable supply-chain signals; maritime and aviation incidents |
geopolitical | Readable geopolitical, military, and policy signals; conflict and political incidents |
Signals are readable when they are global or community, belong to the key's workspace, or are the caller's own private signals.
Provenance
| Value | Meaning |
|---|---|
catalog | Y2's shared catalog: entities, relations, signals, incidents, markets |
ledger | Your workspace's entity ledger |
workspace | Your workspace's research, such as company financial history |
Read budgets
Fusion never scans without a bound. Catalog relations read up to 150 in each direction; each path
party reads its 10 most recently added affects and 10 targets relations, selecting CVEs, threat
actors, and malware for cyber events, and up to 15 signal subjects in the selected window. Financial
history contributes the 12 most recently recorded facts;
up to 5 anchored ledger subjects are folded and 200 workspace topics are read. Incidents and
prediction markets still store entity links as arrays, so they come from the 100 most recently
updated rows. coverage.notes states these limits in each response, and coverage.truncated is true
when any source or output budget omits rows. A truncated response can therefore contain fewer than
200 events. Sources naming both the company and a counterparty retain the direct exposure path.