Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/mnemom-ai:mnemom-ai-policy-api"
All apis
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.
Get an API 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 Specification
openapi: 3.2.0
info:
title: Mnemom Policy 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: Policy
description: Policy evaluation and configuration.
paths:
/policies/evaluate:
post:
operationId: evaluatePolicy
summary: Evaluate an agent's derived policy against tools
description: Evaluate a list of tools against the policy DERIVED from the agent's published canonical alignment card (capabilities + enforcement + escalation triggers). Returns a verdict with detailed violations, warnings, card coverage gaps, and overall coverage percentage. Requires a published canonical card for the agent (PUT /v1/agents/{id}/alignment-card first, else 404). No standalone policy document is accepted — the card is the source of truth (UC-8). `agent_id` must be a string naming an agent the caller may read (`cards:read`); an agent outside the caller's org gets the same 404 as an unknown agent.
tags:
- Policy
security:
- BearerAuth: []
- ApiKeyAuth: []
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- agent_id
- tools
properties:
agent_id:
type: string
description: Agent whose canonical alignment card the policy is derived from. Must have a published canonical card, and the caller must be a member of the agent's org (else 404, the same answer as an agent that does not exist).
tools:
type: array
minItems: 1
items:
type: object
required:
- name
properties:
name:
type: string
description: Tool identifier to evaluate (e.g. "fs_write").
description: Non-empty list of tools to evaluate against the agent's derived policy.
context:
type: string
default: cicd
description: Evaluation surface/context (default "cicd").
dry_run:
type: boolean
default: false
description: When true, the evaluation result is not persisted to policy_evaluations.
responses:
'200':
description: Policy evaluation result
content:
application/json:
schema:
$ref: '#/components/schemas/PolicyEvaluationResult'
'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'
/policies/evaluate/historical:
post:
operationId: evaluatePolicyHistorical
summary: Evaluate a card against an agent's historical traces
description: Replay an agent's recent AIP traces through the policy derived from a card to identify what would have been blocked, escalated, or flagged. By default the agent's current canonical alignment card is used; supply `card_json` to dry-run a hypothetical card instead. Useful for understanding the impact of a card/policy change before rolling it out. No standalone policy document is accepted (UC-8).
tags:
- Policy
security:
- BearerAuth: []
- ApiKeyAuth: []
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- agent_id
properties:
agent_id:
type: string
description: Agent whose historical traces will be replayed. The caller must be an owner, admin or member of the agent's org; otherwise the response is the same 404 as for an unknown agent.
card_json:
type: object
additionalProperties: true
description: Optional hypothetical alignment card to evaluate against. If omitted, the agent's current canonical card is used (404 if the agent has none and no card_json is supplied).
limit:
type: integer
default: 50
maximum: 200
description: Maximum number of recent traces to evaluate (capped at 200).
responses:
'200':
description: Historical evaluation result
content:
application/json:
schema:
type: object
required:
- agent_id
properties:
agent_id:
type: string
card_id:
type: string
description: Card the traces were evaluated against.
total_traces:
type: integer
description: Number of traces returned by the evaluation.
results:
type: array
description: Per-trace verdicts (or {skipped:true} for traces with no tool calls).
items:
type: object
properties:
trace_id:
type: string
verdict:
type: string
violations:
type: array
items:
type: object
warnings:
type: array
items:
type: object
skipped:
type: boolean
summary:
type: object
properties:
pass:
type: integer
warn:
type: integer
fail:
type: integer
skipped:
type: integer
message:
type: string
description: Present only when the agent has no historical traces.
'400':
$ref: '#/components/responses/BadRequest'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/CrossOriginRejected'
'404':
$ref: '#/components/responses/NotFound'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'502':
$ref: '#/components/responses/BadGateway'
components:
responses:
Unauthorized:
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
BadGateway:
description: An upstream dependency returned an invalid response.
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'
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'
CrossOriginRejected:
description: Cross-origin write refused (`cross_origin_rejected`). A state-changing request that carries the browser session cookie must come from a first-party origin (`Origin`, or failing that `Referer`) and must not send a form-style body (text/plain, urlencoded, multipart) the operation does not declare. Bearer and API-key callers are never subject to this check.
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:
PolicyEvaluationResult:
type: object
description: Result of evaluating a CLPI policy against a set of tools or traces.
properties:
verdict:
type: string
enum:
- pass
- warn
- fail
description: Overall evaluation verdict
violations:
type: array
items:
$ref: '#/components/schemas/PolicyViolation'
description: List of policy violations detected
warnings:
type: array
items:
type: object
properties:
tool:
type: string
message:
type: string
description: Non-blocking warnings about potential issues
card_gaps:
type: array
items:
type: object
properties:
capability:
type: string
missing_card_field:
type: string
suggestion:
type: string
description: Gaps between the policy and the alignment card
coverage:
type: number
minimum: 0
maximum: 1
description: Fraction of tools covered by the policy (0.0 to 1.0)
PolicyViolation:
type: object
description: A single policy violation detected during evaluation.
properties:
type:
type: string
enum:
- forbidden
- unmapped
- escalation
- capability_mismatch
description: Type of policy violation
tool:
type: string
description: Tool identifier that triggered the violation
capability:
type:
- string
- 'null'
description: Capability the tool was mapped to, if any
rule:
type:
- string
- 'null'
description: The specific rule or pattern that was matched
reason:
type: string
description: Human-readable explanation of the violation
severity:
type: string
enum:
- low
- medium
- high
- critical
description: Severity level of the violation
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).'