# Neither — Context API

> Context API for agents that need what happened, not what matched.

## Hero

**Context API for agents that need what happened, not what matched.**

Search finds related documents. Neither reconstructs what happened: who was involved, what changed, what evidence supports it, what contradicts it, and what's still missing.

Workflow: connect source systems, maintain the context graph, return what happened — with evidence.

## What agents receive

Example request:

```
GET /api/context/projects?query=renewal
```

Responses include scoped entities, decisions, source references, freshness metadata, and a request ID — designed for agent runtimes that need governed company context, not another one-off retrieval pass.

## How this differs from search

RAG optimizes relevance. Neither optimizes reconstruction. The Context API returns cited projects, people, decisions, and the connections between them so agents reconstruct what happened from the same governed context graph.

## Integration path

- OpenAPI contract for context reads and graph inspection
- Scoped access with workspace keys and capability-scoped permissions