Memory API
Roadmap
What is not built yet, and when it is expected.
Dated items are committed and will ship through the API. The rest have no date yet.
| What | Status today |
|---|---|
| Per-end-user privacy | End of August 2026Retrieval is filtered by audience inside the engine, but /ingest does not yet take an audience key or list, so everything ingested through the API is visible to everything reading that workspace. Adding that parameter is the next milestone. |
| Published rate limits and SLA | End of August 2026No documented limits and no uptime commitment during early access. Tell us the expected volume and we will say whether it is workable. |
| Self-serve keys | End of August 2026Keys are issued by hand during early access. Programmatic issuance, scoping and rotation are not built. |
| Self-serve provisioning | End of August 2026Workspaces are created by us on request. There is no API to create one. This ships together with self-serve keys. |
| Direct graph endpoints | No date yetSearch and CRUD on entities, their memories, their relationships and traversal by hops. The API reference lists the intended routes. Until they ship, /recall returns the same evidence with its sources. |
| Configuration endpoint | No date yetCustom ontology, audiences and ingestion defaults through the API. We apply the same configuration by hand during early access, so ask and it gets done. |
| Versioned routes | No date yetPaths are unversioned and may change. We will warn design partners before a breaking change, but the contract is not frozen yet. |
| Self-hosting | No date yetNot offered. The API runs on our infrastructure only. |