Own Your Knowledge
AI-generated knowledge shouldn't die inside one assistant, one model, or one vendor. Your memories are yours: export the whole knowledge base and re-import it anywhere — a clean round-trip with no lock-in.
Why it matters#
An agent's hard-won context — the observations it recorded, the patterns it noticed — usually evaporates when the employee leaves, the agent is swapped, the model is upgraded, or the vendor changes. A durable knowledge layer keeps it. Because an export carries text, not vectors, it is re-embedded with whatever model is active on import — so a dump made under one embedding model restores cleanly under another. Your knowledge outlives the tools that produced it.
Export#
GET /v1/memory/admin/export
→ {"tenant": {…}, "collections": [...], "memories": [...], "exported_at": "…", "truncated": false}
A JSON download of every collection and memory in your account (tenant-scoped — you only ever see your own data). Memories carry text, category, source, importance, metadata, container tag, type, and timestamps.
Import#
POST /v1/memory/admin/import
{"memories": [{"text": "…", "collection": "team"}, …],
"collections": [...], // optional — pre-create with descriptions
"into_collection": "restored"} // optional — collapse everything into one collection
Re-ingests a dump into your tenant: collections are created as needed, text is re-embedded with
the active model, and ids are reassigned. Returns {imported, skipped, collections}.
(Supersession edges aren't part of an export, so they aren't recreated.)
Round-trip with the SDKs#
# Python — move a knowledge base between instances
dump = source.export_account()
target.import_memories(dump["memories"]) # same shape, anywhere
// JavaScript
const dump = await source.exportAccount();
await target.importMemories(dump.memories, { intoCollection: "restored" });
Need a hard delete instead? POST /v1/memory/admin/delete-account
irreversibly erases the account and its files. See
the operator endpoints.