---
title: "Turn changing signals into context people and AI can reuse"
description: "Learn how Y2 turns changing external signals and private project evidence into source-backed context that people, AI models, and agents can reuse."
canonical: https://y2.dev/what-is-y2/
---

Context as a Service for real-world intelligence

# Turn changing signals into context people and AI can reuse

Context as a Service delivers the relevant, source-backed state of a topic to a person, model, or agent on demand. Y2 builds it from intelligence feeds, recurring research, private project evidence, and an ontology that preserves entities, relationships, time, and provenance.

[Start a Lite trial](https://y2.dev/login)[See how Y2 works](https://y2.dev/use-cases)[Book a demo](https://cal.com/tobalo)

Here, Context as a Service means a real-world intelligence context layer. It is not Containers as a Service, Content as a Service, or a claim that Y2 owns the third-party material cited in a workspace.

A living context layer

Fresh context for every decision surface

Live context refresh

- You
- Your agent
- Your products
- AI models

Context layer

Refresh, reason, and deliver without rebuilding from zero

Source-backedOn demandRecurring

What Y2 keeps current

On demand + recurring cadence

- Knowledge graph

  Entities, relationships, time, and provenance

- Emergent signals

  New evidence and material changes

- Global Knowledge Base

  Reusable public intelligence · Private beta

- Custom briefings

  Source-backed answers for the operating question

Easy to reuse

Reliable by design

Fast to refresh

Durable agent workflows · multi-model reasoning · ontology retrieval · source provenance

The context loop

## A current answer is useful. Reusable context compounds.

Y2 keeps the source trail and connected facts around an answer, so the next workflow can start from prior evidence instead of rebuilding the same search.

1. 01

   ### Observe changing evidence

   Research external signals and private project material around a defined operating question.

2. 02

   ### Resolve identity and time

   Distinguish the people, organizations, places, incidents, and moments that the evidence describes.

3. 03

   ### Connect the source trail

   Preserve relationships, observations, citations, and provenance through an ontology-backed graph.

4. 04

   ### Reason with bounded context

   Give a person or model the evidence relevant to the operating question without flattening its sources.

5. 05

   ### Deliver it to the workflow

   Move reports and structured context into the UI, email, SMS, audio, webhooks, MCP, or API.

6. 06

   ### Compound prior work

   Carry prior evidence into later chats, reports, projects, automations, and API workflows.

Product proof

## Change the model. Keep the context.

Multi-model access is only the interface. The durable advantage is the evidence, graph, operating question, and prior work that can move with it.

### Multi-model chat

Change the model while keeping the conversation and its source-backed workspace context together.

[Explore Y2 Chat](https://y2.dev/docs/chat)

### Evidence-backed signals

Turn emerging changes into decision-support signals connected to their entities, incidents, and sources. Review consequential results before acting.

[See use cases](https://y2.dev/use-cases)

### Knowledge graphs and ontology

Preserve identity, relationships, provenance, and time so a brief becomes reusable context instead of a dead end.

[Read the graph API docs](https://y2.dev/docs/api/intel)

### An AI workspace and context API

Organize private project evidence, run recurring work, and deliver results through MCP, API, or webhooks.

[Explore Projects](https://y2.dev/docs/projects)

Availability

## What Y2 provides today—and what remains limited

| Status            | Capability                                                                  | Boundary                                                                |
| ----------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Available now     | Profiles, Chat, Projects, graphs, signals, delivery, API, MCP, and webhooks | Access and limits follow the active workspace plan.                     |
| Eligible plans    | Automations and new API credentials                                         | Automations and new API keys require Pro or Elite.                      |
| Private beta      | Y2 Global Knowledge retrieval                                               | Production availability is limited to approved private-beta workspaces. |
| Product direction | Broader reuse of authorized workspace context                               | Direction, not a promise of timing or availability.                     |

## Explore the evidence

See the product contracts behind the category language.

[Vision](https://y2.dev/docs/vision)[How Y2 Works](https://y2.dev/blog/how-y2-works)[Projects](https://y2.dev/docs/projects)[Intelligence Chat](https://y2.dev/docs/chat)[Intel API](https://y2.dev/docs/api/intel)[MCP](https://y2.dev/docs/api/mcp)[Pricing and plans](https://y2.dev/pricing)[Intelligence briefings](https://y2.dev/solutions/intelligence-briefings)[Compare OSINT tools](https://y2.dev/blog/best-osint-aggregation-tools-2026)[OpenAPI contract](https://y2.dev/api/openapi.yaml)[Industrial AI agents](https://y2.dev/blog/owned-context-compounds-rented-context-decays)

## Build on context, not another blank prompt

Start with a question in Chat, turn it into recurring research, and deliver the result to your team or agent stack.

[Explore the documentation](https://y2.dev/docs)
