Cortex API · memory.remember

memory.remember

memory:write

Write one durable checkpoint. Idempotent per idempotency_key. Store no secrets and no raw transcripts.

Arguments

Name	Type	Required	Rules / enum
`content`	string	required	Non-empty. No secrets, no raw transcripts.
`idempotency_key`	string	required	Stable and unique per logical write. Reuse only for an exact retry.
`content_kind`	enum	optional	`decision` \| `durable_lesson` \| `fact` \| `observation` \| `session_summary`. Default `observation`.
`session_id`	string	optional	≤256 chars correlation label.
`client_event_ts`	number	optional	Advisory only. Never overrides the server write-time.
`sequence`	integer	optional	≥0. Same-tick ordering tiebreak.

Response (required: idempotency_key, status, memory_ids)

status ∈ {persisted, rejected, unknown}. persisted only when the store reports episodes stored and not partial; a partial / zero / 4xx / 5xx write is rejected; a post-send timeout or transport error is unknown (the write may still have landed).
memory_ids[]: Cortex's write path does not echo stored ids, so the edge derives the entry_id from the idempotency key (mcp_ + sha256). That is the id memory.recall returns for the row.
outcome_known (bool, on unknown), reason (string), replay (bool — true when an idempotency-cache hit replays a prior persisted result).

Example

curl -sS "$CONDUIR_BASE/api/cortex/mcp" \
  -H "Authorization: ApiKey $CORTEX_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool":"memory.remember","arguments":{
        "content":"Cross-vendor memory proven via one key.",
        "idempotency_key":"note-2026-08-21-1",
        "content_kind":"decision"}}'

{ "result": {
    "idempotency_key": "note-2026-08-21-1",
    "status": "persisted",
    "memory_ids": ["mcp_1a2b…"]
} }

Validation test

Runs this exact tool against the live broker (POST /api/cortex/mcp) with the key saved in this browser — the same one the dashboard uses. No key yet? Create one on Your keys (Microsoft sign-in), then come back.

Arguments (editable JSON)