Enterprise · developer reference
Your leadership data, over REST and MCP
One cak_ key. Two doors. A clean read-only /api/v1 for classic integrations, and the MCP endpoint for AI agents. Owner-scoped, scope-gated, rate-limited.
Two doors, one key
/api/v1REST
GET /me, /conversations (+ /:id), /memory, /assessments, owner-scoped, paginated, read-only.
/api/mcpMCP
JSON-RPC 2.0. The same key authenticates member tools, scope-gated to your data.
Read scopes
conversations:readmemory:readassessments:read
Quickstart
Create a key in your dashboard, then call the API.
# 1 — create a key: Dashboard → Settings → API keys (shown once) # 2 — call the API curl https://stuartandrews.me/api/v1/me \ -H "Authorization: Bearer cak_…" # → { "plan": "enterprise", "apiKey": { "scopes": ["conversations:read"] } }
Security
Built for sensitive people data
Keys are sha256-hashed and shown once; entitlement is re-checked live on every request; every query is owner-scoped.
Keys
Hashed, shown once
Access
Only your own data
Entitlement
Checked live
Control
Scoped · revocable
Get your key
API access is included on the Enterprise plan. Enterprise members create keys in Dashboard → Settings → API keys.