REST API

Auth

Bearer auth with workspace API tokens (shv_live_*) or OAuth access tokens (shv_oat_*), both flow through the same chokepoint with identical scope and audit semantics.

• memory.read, read structured memory + memory health
• memory.context, generate context packs and handoffs
• memory.candidates, write review candidates
• continuations.log, log retrieval continuations

Read project context

GET /api/v1/project-memory/projects/{projectId}/context
Authorization: Bearer $SHELVIA_TOKEN

Semantic search

POST /api/v1/project-memory/search
Authorization: Bearer $SHELVIA_TOKEN
Content-Type: application/json

{
  "query": "What did we decide about pricing?",
  "project_id": "PROJECT_ID",
  "mode": "hybrid",
  "limit": 10
}

Generate a context pack

POST /api/v1/project-memory/projects/{projectId}/context-pack
Authorization: Bearer $SHELVIA_TOKEN
Content-Type: application/json

{
  "purpose": "Continue the v2 launch",
  "target_tool": "claude",
  "max_chars": 12000,
  "semantic_ranking": true
}

Create a review candidate

Writes always create review candidates, never trusted memory directly.

POST /api/v1/project-memory/projects/{projectId}/candidates
Authorization: Bearer $SHELVIA_TOKEN
Content-Type: application/json
Idempotency-Key: <uuid>

{
  "type": "decision",
  "title": "Use Paystack for African card payments",
  "content": "Decision body...",
  "source_url": "https://example.com/source"
}