Reference
API reference
Memories
POST /memories
POST /events
GET /memories/search
GET /memories
GET /kv-facts
GET /graph-edges
PATCH /memories/{id}
DELETE /memories/{id}
GET /health
Machine keys (mem_...) work on memories, events, search, list, KV, graph, and health. GET /memories lists without embedding a query. Search is GET /memories/search?q= where q is a natural-language question, not a filter expression. Dashboard Google session still works for list, KV, and graph.
| Param | Type | Description |
|---|---|---|
| session_id | string | Label you invent for a chat or project, not a second tenant. Required on write. Omit on recall for org-wide search. |
| q | string | On search: plain-language question (embedded). Example: what test runner do we use?. On list: optional substring filter, not ranked search. |
| memory_type | string | semantic, episodic, or procedural. |
| as_of | datetime | Optional ISO time. Historical graph edges on recall/search. |
| token_budget | int | Cap how much recall text is returned. Default 2048. |
| limit | int | Max hits on recall. Default 10. |
SDKs and CLI
Prefer the clients over raw HTTP: Python and Node SDKs, CLI. They send Bearer mem_... and map 401/404/429 to typed errors.
Auth
POST /auth/google · GET /auth/me
API keys
POST /api-keys · GET /api-keys · DELETE /api-keys/{id}