Mnemom Presentations API
Investor/data-room presentations + per-viewer grants (MNE-1428, "Inside Mnemom"). Admin create/invite/revoke; authed-user read scoped to active grants. Internal/demo surface, not customer-facing.
Investor/data-room presentations + per-viewer grants (MNE-1428, "Inside Mnemom"). Admin create/invite/revoke; authed-user read scoped to active grants. Internal/demo surface, not customer-facing.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/mnemom-ai:mnemom-ai-presentations-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Mnemom Presentations API
description: Trust infrastructure for AI agents. Transparent alignment verification, behavioral drift detection, and accountability primitives.
version: 1.0.0
contact:
name: Mnemom
url: https://mnemom.ai
email: support@mnemom.ai
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0
servers:
- url: https://api.mnemom.ai/v1
description: Production
security:
- BearerAuth: []
- ApiKeyAuth: []
tags:
- name: Presentations
description: Investor/data-room presentations + per-viewer grants (MNE-1428, "Inside Mnemom"). Admin create/invite/revoke; authed-user read scoped to active grants. Internal/demo surface, not customer-facing.
paths:
/presentations:
get:
operationId: listMyPresentations
summary: List presentations granted to the current user
description: Returns the presentations the caller holds an ACTIVE grant for (revoked_at IS NULL and not expired), each with the caller's tier. Drives the `/dashboard/presentations/` menu — an empty list means the menu is hidden. Authed user. MNE-1428.
tags:
- Presentations
security:
- BearerAuth: []
responses:
'200':
description: Presentations granted to the caller (may be empty).
content:
application/json:
schema:
type: object
required:
- presentations
properties:
presentations:
type: array
items:
type: object
description: A granted presentation, flattened with the caller's grant metadata.
required:
- id
- slug
- title
- status
- tier
- grant_id
properties:
id:
type: string
format: uuid
slug:
type: string
description: URL-safe id, e.g. 'inside-mnemom'.
title:
type: string
agent_id:
type:
- string
- 'null'
description: The presentation's agent (e.g. Aletheia). prod agents.id; no FK.
status:
type: string
enum:
- draft
- live
- archived
created_by:
type: string
description: Principal id of the minting admin. Opaque principal id, same shape as `User.id` (a Zitadel subject on the Azure cells, a uuid for legacy Supabase users); never parse it as a uuid.
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
grant_id:
type: string
format: uuid
tier:
type: string
enum:
- L1
- L2
- L3
expires_at:
type:
- string
- 'null'
format: date-time
'401':
$ref: '#/components/responses/Unauthorized'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
/presentations/{slug}:
get:
operationId: getPresentation
summary: Get a presentation by slug (with the caller's tier)
description: Returns the presentation and the caller's granted tier. 404 if no such presentation; 403 if the caller holds no active grant for it. Authed user. MNE-1428.
tags:
- Presentations
security:
- BearerAuth: []
parameters:
- name: slug
in: path
required: true
schema:
type: string
description: The presentation slug.
responses:
'200':
description: The presentation + the caller's tier.
content:
application/json:
schema:
type: object
required:
- presentation
- tier
properties:
presentation:
type: object
required:
- id
- slug
- title
- status
- created_by
- created_at
- updated_at
properties:
id:
type: string
format: uuid
slug:
type: string
description: URL-safe id, e.g. 'inside-mnemom'.
title:
type: string
agent_id:
type:
- string
- 'null'
description: The presentation's agent (e.g. Aletheia). prod agents.id; no FK.
status:
type: string
enum:
- draft
- live
- archived
created_by:
type: string
description: Principal id of the minting admin. Opaque principal id, same shape as `User.id` (a Zitadel subject on the Azure cells, a uuid for legacy Supabase users); never parse it as a uuid.
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
tier:
type: string
enum:
- L1
- L2
- L3
expires_at:
type:
- string
- 'null'
format: date-time
voiceEnabled:
type: boolean
description: 'Whether Aletheia voice mode is enabled for this caller. The FE gates the voice toggle on this. Always true on a 200: presentation access alone now grants both chat and voice, so a caller with no active grant gets a 403 rather than this payload with voiceEnabled:false.'
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
/presentations/{slug}/accept:
post:
operationId: acceptPresentationInvite
summary: Accept a presentation invite (attach the grant to the caller)
description: 'The endpoint the invite email''s CTA lands at after the recipient signs in / signs up. The single-use token comes from the body `{token}` or the `?token=` query param; it''s hashed and matched to a pending grant for THIS presentation. On success the grant is attached to the caller (user_id + accepted_at set, token consumed) and the caller''s tier is returned. The invite email is address-specific: the caller''s account email MUST match the grant email (case-insensitive) or a 403 is returned. Authed user. Requires an `Idempotency-Key` header. MNE-1428.'
tags:
- Presentations
security:
- BearerAuth: []
parameters:
- name: slug
in: path
required: true
schema:
type: string
description: The presentation slug.
- name: token
in: query
required: false
schema:
type: string
description: The single-use invite token. May instead be supplied in the JSON body as `token`.
- name: Idempotency-Key
in: header
required: true
schema:
type: string
description: Idempotency key (UUID). Replays within 24h return the same response.
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
token:
type: string
description: The single-use invite token.
responses:
'200':
description: Invite accepted (or idempotently already accepted by this caller). Returns the presentation + the caller's tier.
content:
application/json:
schema:
type: object
required:
- presentation
- tier
properties:
presentation:
type: object
required:
- id
- slug
- title
- status
- created_by
- created_at
- updated_at
properties:
id:
type: string
format: uuid
slug:
type: string
description: URL-safe id, e.g. 'inside-mnemom'.
title:
type: string
agent_id:
type:
- string
- 'null'
description: The presentation's agent (e.g. Aletheia). prod agents.id; no FK.
status:
type: string
enum:
- draft
- live
- archived
created_by:
type: string
description: Principal id of the minting admin. Opaque principal id, same shape as `User.id` (a Zitadel subject on the Azure cells, a uuid for legacy Supabase users); never parse it as a uuid.
created_at:
type: string
format: date-time
updated_at:
type: string
format: date-time
tier:
type: string
enum:
- L1
- L2
- L3
accepted:
type: boolean
already_accepted:
type: boolean
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'409':
$ref: '#/components/responses/Conflict'
'410':
description: The invite has expired.
content:
application/json:
schema:
type: object
required:
- error
properties:
error:
type: object
properties:
code:
type: integer
message:
type: string
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
/presentations/{slug}/chat:
post:
operationId: presentationChat
summary: Send a governed turn to the presentation's agent (Aletheia)
description: 'One governed Aletheia turn (MNE-1428): routed through the Mnemom gateway (Safe House / AIP / CLPI / back-door screen in-path), executing read-only Mnemom MCP tools + a curated readiness brief scoped to the viewer''s grant tier. Returns her answer, the per-round verdict cascade ({cfd,aip,policy,cbd}), citations, and a compact attestation. Authed user; requires an ACTIVE grant for the presentation. A Safe House hard-block is a governance success, not an error: it returns 200 with `blocked:true` and no answer. Chat is intentionally NOT idempotent (each turn is new), so no Idempotency-Key is required.'
tags:
- Presentations
security:
- BearerAuth: []
parameters:
- name: slug
in: path
required: true
schema:
type: string
description: The presentation slug.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- message
properties:
message:
type: string
description: The viewer's turn.
maxLength: 4000
deck:
type: string
description: The deck's own text, handed over by the page that is already rendering it, so Aletheia reads it as her primary source. Capped server-side.
history:
type: array
description: Optional prior turns for multi-turn context. Only {role:'user'|'assistant', content:string} entries are honored; the newest 20 are kept.
items:
type: object
properties:
role:
type: string
enum:
- user
- assistant
content:
type: string
responses:
'200':
description: The turn's result. `ok:false` with `blocked:true` means Safe House withheld the response (governance success).
content:
application/json:
schema:
type: object
required:
- ok
- blocked
- answer
- citations
- verdicts
- attestation
- tier
properties:
ok:
type: boolean
blocked:
type: boolean
answer:
type:
- string
- 'null'
tier:
type: string
enum:
- L1
- L2
- L3
citations:
type: array
items:
type: object
properties:
tool:
type: string
detail:
type: string
verdicts:
type: array
items:
type: object
properties:
round:
type: integer
cfd:
type:
- string
- 'null'
aip:
type:
- string
- 'null'
policy:
type:
- string
- 'null'
cbd:
type:
- string
- 'null'
advisory:
type:
- string
- 'null'
attestation:
type: object
properties:
agent_id:
type:
- string
- 'null'
session:
type:
- string
- 'null'
model:
type: string
aip_checkpoint_id:
type:
- string
- 'null'
screened_intervention:
type: boolean
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'502':
description: The governed chat runtime is currently unavailable.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'503':
description: Presentation chat is not configured on this deployment.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/presentations/{slug}/voice/register:
post:
operationId: presentationVoiceRegister
summary: Start an Aletheia voice session for the presentation
description: Opens a voice session for the presentation's agent (Aletheia, MNE-1428 voice). Creates a Retell web call, mints a short-lived scoped voice-grant token, and hands it plus the deck + scope to the separate voice backend, which then proxies each spoken turn to `POST /v1/presentations/{slug}/chat` bearing that token. Governance (Safe House / tier / tools) stays entirely in the chat runtime — this endpoint re-implements none of it, and the token is authentication-only (the active grant remains the sole authority). Authed user; requires an ACTIVE grant. Returns the Retell web-call access token + call id for the browser SDK. Not idempotent (each session is new), so no Idempotency-Key is required.
tags:
- Presentations
security:
- BearerAuth: []
parameters:
- name: slug
in: path
required: true
schema:
type: string
description: The presentation slug.
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
deck:
type: string
description: The deck's own text, handed to the voice backend so Aletheia reads it as her primary source. Capped server-side.
responses:
'200':
description: The voice session was created. Returns the Retell web-call access token + call id for the browser's Retell web-call SDK.
content:
application/json:
schema:
type: object
required:
- access_token
- call_id
properties:
access_token:
type: string
description: The Retell web-call access token for the browser SDK.
call_id:
type: string
description: The Retell call id.
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'502':
description: The voice provider or the voice backend failed to start the session.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'503':
description: Voice is not configured on this deployment.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
responses:
Conflict:
description: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Unauthorized:
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
InternalServerError:
description: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
TooManyRequests:
description: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
headers:
Retry-After:
description: Seconds to wait before retrying.
schema:
type: integer
minimum: 1
X-RateLimit-Limit:
description: Requests permitted per window.
schema:
type: integer
X-RateLimit-Remaining:
description: Requests remaining in the current window (0 on a 429).
schema:
type: integer
minimum: 0
X-RateLimit-Reset:
description: Unix epoch seconds at which the current window resets.
schema:
type: integer
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Forbidden:
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
BadRequest:
description: Bad request
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
NotFound:
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
schemas:
Error:
type: object
description: Canonical error envelope (ADR-API-001 conv 1). `error` is always an object — never a bare string. Every 4xx/5xx response across the API conforms to this shape; the runtime helper is `src/http-errors.ts::buildErrorBody`.
required:
- error
properties:
error:
type: object
required:
- code
- message
properties:
code:
type: string
pattern: ^[a-z][a-z0-9_]*$
description: 'Stable, machine-matchable failure identifier (lowercase snake_case). Clients may branch on this; the string is part of the contract.
**Status-class defaults** — emitted when no caller code is supplied (`errorCodeForStatus(status)`): `bad_request` (400), `unauthorized` (401), `forbidden` (403), `not_found` (404), `method_not_allowed` (405), `conflict` (409), `gone` (410), `precondition_failed` (412), `payload_too_large` (413), `unsupported_media_type` (415), `unprocessable_entity` (422), `precondition_required` (428), `rate_limited` (429), `internal_error` (500), `not_implemented` (501), `bad_gateway` (502), `service_unavailable` (503), `gateway_timeout` (504). Fallback `error` for unmapped statuses.
**Caller-supplied codes** — handlers may pass an explicit `code` for a specific failure class. Examples: `agent_not_found`, `invalid_hash_proof`, `already_linked`, `idempotency_conflict`, `feature_gated`, `schema_validation_failed`, `no_token`, `bad_canonical_payload`.
**Care-framed sub-resource codes** — the cards-as-primitive surface passes its stable care code-string straight through as `error.code`. Examples: `if_match_absent`, `if_match_stale`, `if_match_malformed`, `primitive_validation_failed`.'
message:
type: string
description: Human-readable, care-framed explanation of the failure.
details:
description: 'Optional structured context for the failure (any JSON value: object, array, or primitive). Common shapes: validation findings list, idempotency-conflict diff, `{presented_etag, current_etag}` on a stale `If-Match`, etc. Mirrors the helper''s `details?: unknown`.'
securitySchemes:
BearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: 'Supabase JWT token in Authorization: Bearer header'
ApiKeyAuth:
type: apiKey
in: header
name: X-Mnemom-Api-Key
description: Mnemom API key (mnm_... format)
ServiceRole:
type: http
scheme: bearer
bearerFormat: JWT
description: Supabase service role bearer JWT. Used by /blog admin operations that talk directly to Supabase. NOT used by /internal/* or /v1/arena/internal/* — those use the custom-header schemes below.
InternalKeyAuth:
type: apiKey
in: header
name: X-Internal-Key
description: Internal service-to-service shared secret, timing-safe compared against INTERNAL_API_KEY. Used by /internal/* gateway routes (compose, agents, webhooks emit).
ServiceKeyAuth:
type: apiKey
in: header
name: X-Service-Key
description: Service-to-service shared secret, timing-safe compared against MNEMOM_SERVICE_KEY. Used by /v1/arena/internal/*, /v1/on-chain/*, and the /v1/internal/* readers consumed by the reputation cron.
CoherenceTokenAuth:
type: http
scheme: bearer
description: Per-cell coherence bearer token. Provisioned in 1Password vault `mnemom-coherence` (one item per receiver). Value compared against COHERENCE_<NAME>_SERVICE_TOKEN_EXPECTED. Used by /v1/internal/coherence/* and /v1/internal/governance/dispatch.
ArenaCandidateTokenAuth:
type: http
scheme: bearer
description: Dedicated arena writer token (ADR-004 §"Arena dedicated writer token"). Compared against ARENA_RECIPE_CANDIDATE_TOKEN. The token's only capability is writing recipe candidates with writer_identity='arena-bypass' (stamped server-side). Used by POST /v1/internal/recipe-candidates.
CustomerVoiceTokenAuth:
type: http
scheme: bearer
description: Customer Voice API bearer token. Timing-safe compared against CUSTOMER_VOICE_API_TOKEN. Grants access to all /v1/internal/feedback/* endpoints (MNE-1876). No customer-facing or reporter-read capability.
CookieAuth:
type: apiKey
in: cookie
name: mnemom_session
description: 'HttpOnly, Secure, SameSite=Lax cookie issued by /v1/auth/sign-in (or the SSO / email-callback flows). The value is an AES-256-GCM-encrypted blob of {access_token, refresh_token, issued_at, auth_method}. Browser clients include this automatically with `credentials: "include"`.'
LicenseJwtAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: License JWT (HS256, HMAC-signed with LICENSE_SIGNING_SECRET). Used by self-hosted deployment instances to authenticate `/v1/deployments/heartbeat`. Not interchangeable with the Supabase user JWT.
AgentAuth:
type: apiKey
in: header
name: X-Mnemom-Agent-Proof
description: 'Agent possession proof: the full SHA-256 hex digest of `${apiKey}|${agentName}` (or `${apiKey}` for an unnamed singleton agent) — the same `hash_proof` primitive used by POST /v1/agents claim, link-agent, and verify-binding. The server resolves the agent by `agent_hash = proof[:16]`. The agent''s *own* identity (ADR-API-001 third auth class) — distinct from ApiKeyAuth (`X-Mnemom-Api-Key`, which resolves a user/account, not an agent).'