Better signal
Live, structured, user-maintained context — not stale forms or siloed copies.
For services & developers
Better services without owning the warehouse
Users hold structured, live personal context. You integrate via computation contracts — query in place, return approved results, compete on intelligence not database size.
Why integrate
Four wins for your product
Offer better services with user-permissioned data — without storing the liability yourself.
Less liability
Query in place under contract. No warehouse to breach, erase, or audit.
Lower cost
Integrate once via manifest. Skip duplicate collection, storage, and DPO overhead.
Trust by default
Purpose, space scope, permission tier, and consent ledger — user approves every relationship.
The shift
Computation contracts, not data dumps
Give us all your data
Permanent copy in your warehouse. Stale the moment it lands. Liability on you.
Run this approved computation
User approves purpose and space. You query live at source. Return the result — optionally write insights back. Not the vault.
How it works
Context exchange in six steps
The user is the root database. You are a temporary processor — query live, deliver value, optionally write back.
- 01
Approve
User picks counterparty, purpose, spaces, and permission tier.
- 02
Read
Partner queries scoped context live — manifest + query API, no warehouse copy.
- 03
Deliver
Your product returns value: recommendation, eligibility, automation.
- 04
Write back
Optional insights compound the user's graph under delegated write.
- 05
Audit
Every read and write visible in Exchanges and the consent ledger. Revoke anytime.
Users can test the loop with the built-in Autograf demo: Try the demo exchange.
Integration paths
Ship today with manifests and MCP
Computation contract
User creates a contract with counterparty, purpose, space, and permission tier. You receive manifest and query URLs.
Contracts in dashboard →Share token + manifest
GET /api/share/[token]?format=manifest returns capability document. POST /api/share/[token]/query runs scoped computation.
Shares in dashboard →MCP integration
Connect Cursor, Claude Code, or custom agents via OAuth-scoped MCP grants. Activity lands in the user's graph under contract.
MCP in dashboard →Context exchange (read + write-back)
Full bidirectional loop: query scoped context, deliver value, optionally write insights back. Users see both directions in Exchanges.
Exchanges in dashboard →Developer quickstart: autograf/docs/integrating-services.md in the repo · Concept: concepts/computation-contracts.md
Use cases
What you can build
Travel recommendations
Read travel history and calendar under family space. Suggest options — never sell the profile.
Affordability checks
Query financial space for a computation. Return yes/no — not full transaction history.
Work scheduling
Read work space for project context and hours. Prepare meetings without uploading everything.
Agent skills (MCP)
Cursor, Claude Code, and custom agents connect via scoped MCP grants.
Health write-back
Read dietary space for meal planning; write lab summary back as a Note under delegated write.
Permission tiers
Language users understand
Map technical permissions to tiers your users can approve with confidence.
Local only
Data stays in the user's space. Read and query — nothing exported.
Private compute
External AI can answer questions. Raw data is not stored outside the space.
Approved export
Specific outputs can leave. Query plus controlled export.
Temporary access
Expires automatically. Good for trials and one-off checks.
Delegated write
Can write insights back into the user's graph with provenance.
Sensitive data
Health, finance, or legal spaces — extra confirmation required.
User-side first
Users adopt before you integrate
Single-player value — private AI memory — creates the structured graph companies later query.
- Capture anywhere — Paste, URLs, MCP record from Cursor & Claude
- Connectors — Gmail, Calendar, Slack, GitHub via OAuth sync
- Recall everywhere — MCP recall, assistant, scoped query for services
- RDF import — Turtle, JSON-LD for power users