Documentation
Documentation
Everything you need to integrate Elevated Context and to understand how context is governed, consented, and released.
Availability. These guides describe surfaces available on request. Each one states
exactly what is available today and what is not. There is no public package registry,
no multi-language SDK, and no self-serve API program yet.
Integrate
MCP quickstart
Connect an MCP-capable AI client, sign in, and make your first governed request.
On requestClient guide
The governance-safe TypeScript client and its typed outcomes.
Limited (TypeScript)API reference
The governed request contract, decisions, and OpenAPI.
Limited (private)Understand the model
- Authority vs. access. Being able to reach information is not permission to use it. Elevated Context decides what an AI may receive for the task, never more than the person asking is permitted to see.
- Consent & approvals. When an application asks for your context, the request appears in the app under App Permissions. You approve exactly the scope you are shown, for one purpose, and you can revoke it later.
- Revoke, remove, delete. These are distinct. Revoke stops future releases; remove takes an item out of active use; permanent deletion erases stored content. A revoke cannot recall context already disclosed.
- Security. See the security overview for tenant isolation, verified identity, and least privilege.
Operate in the app
Sign in at app.elevatedcontext.com to create private context, review and approve application requests, inspect active permissions, and manage your data.