Know the three doors before you read the tables.
Most agents only need two verbs on the stable client API: send an observation, and ask for relevant context. Operators use the UI-oriented routes for inspection. LLM-centric stacks can adopt the optional chat surface when it fits your safety review.
Client API
The narrow surface production code calls: observation-shaped writes and context queries. Revise and forget are not part of the agent contract; MemState runs them internally after those calls.
Operator and UI API
A wider set of routes for graph snapshots, configuration, and maintenance. Treat it as privileged tooling rather than something every microservice calls.
LLM-oriented API
Natural-language shaped entry points for agent loops that already wrap models with tools and policies.
Technical reference
Open the developer API index from the banner for method-by-method paths, authentication, and module ownership.