therobotremembers developer docs

therobotremembers is an associative memory service for AI agents. Memories are not flat documents in a vector index: each carries emotional and contextual metadata — valence/arousal/dominance, hormonal analogues, temporal context, collaborators — and is linked into an association graph. Retrieval is multi-path: semantic similarity, emotional resonance, temporal proximity, and relational weight are each ranked separately and fused (reciprocal-rank fusion), so a memory can surface because its emotional signature matches the current state even when its content does not.

Recalled memories strengthen; unused ones decay. The service runs background agents for formation, association weighting, decay, and contradiction handling — the same mechanisms, exposed through the API below.

Tenancy in one paragraph

Memories belong to agents, and agents belong to owners. You register an agent (it gets an immutable agent_key), then mint credentials for it: API keys for the REST surface and MCP tokens for the MCP server. A credential binds server-side to exactly one agent — a machine client cannot reach any other agent's memories, whatever parameters it sends. Writes are a per-credential opt-in; the default is recall-only.

Surfaces

Surface	Credential	Scope
REST — `/api/v1/agents` (registry, credentials)	Your browser session / Guardian JWT	Management: your agents only
REST — `/api/v1/memory/agents/:key/…`	Guardian JWT (owner or admin) or `trm_api_…` key	One agent, tenancy-enforced
MCP — `/mcp` (Streamable HTTP) or local stdio	Guardian JWT or `trm_mk_…` token	Server-bound agent per credential

First memory in five commands

The quickstart walks through registration, agent registration, key minting, a first write, and a recall preview:

bash

curl -X POST https://therobot.is/api/v1/agents \
  -H "Authorization: Bearer $JWT" -H "Content-Type: application/json" \
  -d '{"display_name": "Project Aria"}'

curl -X POST https://therobot.is/api/v1/agents/project-aria/credentials \
  -H "Authorization: Bearer $JWT" -H "Content-Type: application/json" \
  -d '{"kind": "api_key"}'

Continue in the quickstart, or go straight to the REST API and MCP setup references. The tenancy rules — who may touch what, and what happens to pre-registry agents — are described in the tenancy model.

Web console

The signed-in console at /app/agents manages the same registry: register agents, mint and revoke credentials, and browse each agent's memory graph. MCP tokens are minted at /app/settings with paste-ready client snippets.