---
title: "Put reusable intelligence context to work"
description: "See how Y2 turns changing signals into briefs, investigations, graphs, and reusable context for markets, geopolitics, cyber, supply chains, and AI agents."
canonical: https://y2.dev/use-cases/
---

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 7-day trial](https://y2.dev/login)[See playbooks](#how-to-use)

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.

01

### Profile

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

02

### Research

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

03

### Brief

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

04

### Graph

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

05

### 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. 1

   Write one clear operating question, not a vague theme.

2. 2

   Create a profile with topic, schedule, and who needs the brief.

3. 3

   Add practical focus terms: names, places, materials, risk types your team already uses.

4. 4

   Review the first report for what changed, why it matters, and what to watch next.

5. 5

   Tune the topic if it is too broad or missing risk classes, then keep the schedule aligned to decisions.

[Open My Profiles](https://y2.dev/app/infoops/my-profiles)[Read profiles docs](https://y2.dev/docs/profiles)

Tools you will use

- My Profiles for topic setup and schedules
- Daily, weekly, or monthly delivery rhythm
- Email, SMS, audio, and webhooks

[Read the full guideHow Y2 Works](https://y2.dev/blog/how-y2-works)

[Set up a recurring briefing](https://y2.dev/solutions/intelligence-briefings)

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.](https://y2.dev/blog/how-y2-works)[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.](https://y2.dev/blog/supply-chain-risk-management-with-y2)

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 7-day trial](https://y2.dev/login)[Explore the API](https://y2.dev/docs/api)[Book a demo](https://cal.com/tobalo)