The Engine has three memory stores — episodes, knowledge, and the social graph — plus a “soul” representing the user’s core identity and learned patterns. Memory updates as the agent runs; these endpoints let you read and move it. All memory endpoints requireDocumentation Index
Fetch the complete documentation index at: https://internal.september.wtf/llms.txt
Use this file to discover all available pages before exploring further.
X-Engine-Key.
POST /memory/knowledge/search
Search the knowledge store with hybrid (vector + keyword) scoring.| Field | Type | Required | Default | Purpose |
|---|---|---|---|---|
query | string | yes | — | The natural-language query. |
limit | int | no | 20 | Max results (1–100). |
POST /memory/episodes/search
Same shape as knowledge search. Returns episodes — past events, conversations, outcomes.POST /memory/social/search
Search the social graph (people, relationships).GET /memory/soul
Get a summary of the soul.GET /memory/soul/full
Same as/memory/soul but with all metadata and history. Larger payload.
GET /memory/export
Export the entire memory as a portable JSON bundle. Useful for backup or migration to a new Engine instance. Response is an opaque JSON blob — pass it back to/memory/import to
restore.
POST /memory/import
Import a memory bundle previously produced by/memory/export.
See also
- Memory in the architecture overview for how the stores are organized.
- Build a coding agent for an example of how memory threads back into the agent loop.

