Use cases

Put reusable intelligence context to work

Start with an operating question. Y2 gathers evidence, connects it to entities and prior work, creates a sourced brief, and delivers the result where your team or agents already work.

Start Trial See playbooks

How Y2 works

A context loop, not a one-off prompt

Many tools can summarize text. Y2 keeps the source trail, organizes evidence, writes a brief, extracts signals, and connects durable facts in a knowledge graph so later work can reuse them.

Profile

The profile is the contract: topic, schedule, audience, and delivery. It answers what changed, why it matters, and what to do next.

Research

Y2 breaks the topic into smaller parts, gathers sources in parallel, dedupes evidence, and keeps citations attached.

Brief

Synthesis turns evidence into a human-readable report: bottom line, key findings, analysis, outlook, and sources.

Graph

Signals, events, and entities are extracted with provenance and fused into the shared ontology in the background.

Deliver

Send the output by email, SMS, audio, webhook, map context, or API so teams can act without re-searching.

Bottom line: the report is only one artifact. Around it are findings, citations, signals, entities, and graph relationships that improve the next workflow.

How to use it

Pick a workflow, then follow the steps

Each tab is a practical playbook. Keep the first profile narrow. Review the first report. Then deliver it into dashboards, chat, tickets, or your API stack.

InfoOps

Operating question: what topic do I need monitored on a repeatable schedule?

A Y2 profile is not a saved search. It is a recurring intelligence workflow for a company, market, region, risk theme, or operating question you care about.

1
Write one clear operating question, not a vague theme.
2
Create a profile with topic, schedule, and who needs the brief.
3
Add practical focus terms: names, places, materials, risk types your team already uses.
4
Review the first report for what changed, why it matters, and what to watch next.
5
Tune the topic if it is too broad or missing risk classes, then keep the schedule aligned to decisions.

Open My Profiles Read profiles docs

Profiles + API

Operating question: which suppliers, ports, materials, or routes could be disrupted this week?

Supply chain risk arrives as scattered signals. Turn them into one narrow profile for weekly briefings, daily monitoring, and internal dashboards.

1
Pick one risk to monitor first: suppliers, shipping lanes, commodities, or fragile customer commitments.
2
Create a profile with a plain-language topic and a schedule that matches your decision cycle.
3
Add focus terms your team actually uses: supplier names, ports, countries, materials, strike, sanctions, flood, outage.
4
Read the first report like an operating brief and narrow the topic if it wanders.
5
Push summaries into procurement dashboards, Slack, tickets, or your warehouse via API or webhooks.

Create a risk profile Read the supply-chain guide

FININT

Operating question: what market, energy, or macro pressure should change our stance this week?

Use FININT for live market context, then attach a profile when you need a recurring brief on a ticker, commodity, region, or theme.

1
Open Markets and scan energy, macro, and related volatility signals.
2
Name the decision the brief should support: hedge, monitor, rebalance, or escalate.
3
Create a profile around the asset class, company, commodity, or policy risk you care about.
4
Deliver the brief before the meeting or market open, not after the consensus forms.

Open Markets Create a market profile

Situation Room

Operating question: what changed in this country, theater, or route, and who is exposed?

The Situation Room is a live OSINT map. Use it for current awareness, then create profiles when a region needs recurring coverage.

1
Open the Situation Room and focus on the region, conflict, disaster, or route that matters.
2
Use country context for instability, timelines, and a fast AI readout.
3
Seed a profile when the same theater needs daily or weekly coverage.
4
Link related companies, ports, or assets in Explorer when the event becomes an investigation.

Open Situation Room Read OSINT docs

Cyber

Operating question: which threats, CVEs, or incidents affect assets we care about?

Cyber in Y2 sits beside OSINT and markets so security risk is part of the same operating picture, not a separate silo.

1
Open Cyber and scan incidents, threat clusters, and CVE context.
2
Create a profile for vendors, software stacks, threat actors, or exposure themes you own.
3
Review briefs for patch, monitor, escalate, or defer style decisions with sources attached.
4
Use webhooks or the API when a critical vendor or CVE should open a ticket automatically.

Open Cyber Create a cyber profile

Explorer

Operating question: how do this company, event, market, and risk connect?

Explorer turns a lead into a board of entities and relationships. Use it when one brief is not enough and you need connected context.

1
Seed a board from a company, incident, market, port, or person.
2
Traverse relationship edges instead of re-running isolated searches.
3
Enrich the graph when you need more context, keeping source structure intact.
4
Pull the same entity graph through the Intel API for internal tools if needed.

Open Explorer Read Intel API docs

Developer

Operating question: how do I get Y2 reports and profiles into systems we already run?

Profiles are not only for the dashboard. Create or list profiles with the API, pull the latest report, and post into Slack, tickets, docs, or a warehouse.

1
Create a workspace API key with the scopes you need (profiles and reports are the usual start).
2
Create a profile in the dashboard or POST /profiles with the same fields you would type by hand.
3
List reports by profileId and fetch full content when you need sources or audio metadata.
4
Prefer webhooks when you want Y2 to push each new report instead of polling.
5
Use the API Workbench to copy tested curl, TypeScript, or Python snippets before shipping.

Open API docs Open API Workbench

Go deeper

The same narrative in full

These guides explain the engine and a real supply-chain setup with the same language used on this page.

How Y2 WorksThe engineering map: recursive research, findings, synthesis, provenance, ontology enrichment, and fusion.Supply Chain Risk with Y2A concrete setup: pick the risk, create a profile, review the first report, then pull it into internal tools with the API.

Ready to get started?

Define the risk. Create the profile. Ship the brief.

Start a 7-day Lite trial, open a product surface, or connect the API so intelligence lands where decisions already happen.

Start Trial Explore the API Book a demo