Documentation Index
Fetch the complete documentation index at: https://docs.mnemom.ai/llms.txt
Use this file to discover all available pages before exploring further.
Available under X-Mnemom-Version: 2026-04-15 and later. The legacy
/card, /policy, /cfd/config, /org-card-exempt, and /card-template
endpoints were removed in this cutover rather than deprecated — see
ADR-008 for the rationale. Two cards per agent
Every agent on Mnemom is governed by two YAML cards:
| Card | Authors | Answers |
|---|
| Alignment card | Agent operator, Org admin | Who is this agent? What may it do? What does it commit to? |
| Protection card | Security operator | How is this agent protected from threats? |
Endpoint surface
Per-agent
| Method | Path | Purpose |
|---|
| GET | /v1/agents/:id/alignment-card | Read the canonical alignment card |
| PUT | /v1/agents/:id/alignment-card | Publish a new alignment card (YAML or JSON) |
| GET | /v1/agents/:id/protection-card | Read the canonical protection card |
| PUT | /v1/agents/:id/protection-card | Publish a new protection card |
| GET | /v1/agents/:id/exemptions | List active exemptions |
| POST | /v1/agents/:id/exemptions | Grant an exemption (org-admin only) |
| DELETE | /v1/agents/:id/exemptions/:exemption_id | Revoke an exemption |
Per-org
| Method | Path | Purpose |
|---|
| GET | /v1/orgs/:id/alignment-template | Read the org alignment template |
| PUT | /v1/orgs/:id/alignment-template | Update the template (triggers org-wide recompose) |
| DELETE | /v1/orgs/:id/alignment-template | Clear the template |
| GET | /v1/orgs/:id/protection-template | Read the org protection template |
| PUT | /v1/orgs/:id/protection-template | Update the template (triggers org-wide recompose) |
| DELETE | /v1/orgs/:id/protection-template | Clear the template |
Content negotiation
All card endpoints are YAML-first.
| Request header | Response body |
|---|
Accept: text/yaml (default) | YAML |
Accept: application/yaml | YAML |
Accept: application/json | JSON |
Content-Type: text/yaml) or JSON
(via Content-Type: application/json with the raw card as the body, or
wrapped as { "card_yaml": "<yaml string>" } or { "card_json": {...} }).
Every PUT, POST, or DELETE must carry:
Idempotency-Key: <opaque 24h-unique string>
422 Idempotency-Key conflict.
Cross-cutting contracts
Every response from a card endpoint includes X-Mnemom-Schema, every
mutation writes a governance_audit_log row before responding, and every
mutation emits a webhook event. See the Governance guarantees page for details.
What is NOT available through these endpoints
- Trust edges, team cards, team coherence, fault lines — separate endpoints under
/v1/teams/…; unchanged by UC-4.
- Safe House operational endpoints (quarantine, canary, patterns, metrics, sessions, compliance reports) — preserved; unchanged by UC-4.
- Policy evaluation —
/v1/policies/evaluate and /v1/policies/evaluate/historical are preserved as a distinct concern (evaluate a card’s enforcement section against a tool manifest).
