API reference

The public API focuses on developer memory flows. Handwritten pages are the primary reference in this release; the machine-readable OpenAPI bundle remains available for client generation and agent tooling.

Core endpoints

Page	Endpoint	Use it for
Retain	POST /api/v2/containers/{container_tag}/retain	Save a compact fact or candidate content.
Recall	POST /api/v2/containers/{container_tag}/recall	Retrieve governed memory context.
Agent Context	POST /api/v2/containers/{container_tag}/agent/context	Build pre-turn prompt-ready context.
Writeback	POST /api/v2/containers/{container_tag}/agent/writeback	Capture post-turn outcomes.
Reflect	POST /api/v2/containers/{container_tag}/reflect	Answer a question using memory.
Courtroom	GET /api/v1/memories/{memory_id}/courtroom	Inspect evidence and verdicts.
OpenAI-compatible Gateway	POST /v1/chat/completions, POST /v1/responses	Use familiar model-client envelopes with memory.
MCP	POST /mcp	Connect agent tools.

Shared behavior

• Auth uses scoped keys. Admin keys are for operators, not normal agents.
• container_tag defaults to jeethendra for first-party integrations.
• Public UX and API diagnostics should prefer trust_bucket over legacy raw confidence and trust_score.
• Missing evidence, provider outages, or fallback paths should be reported as degraded/unavailable rather than hidden.

OpenAPI browser and machine-readable spec

Browse the API and schemas inline:

https://docs.jithendranara.dev/api-reference/openapi

The curated public OpenAPI bundle is available at:

https://docs.jithendranara.dev/openapi.public.json

It intentionally excludes admin, private auth, migration, proof, destructive, and internal GCP bridge routes.

Next steps

• Read Authentication.
• Review Errors.
• Try the quickstart.