Use cases
One memory store your tools can share, plus an OpenAI-compatible API for the models. Your agents keep their context between sessions and across tools. Namespaces keep it organized; every view (wiki, graph, git, files) reads the same store.
Coding agents
Architecture decisions, conventions, error post-mortems and the reason that odd workaround exists. Your agent queries them with no large language model in the retrieval step. Monthly coding packages with memory included are coming soon.
projects.build.notes · projects.build.libraryResearch
Papers, quotes, sources and your own margin notes, organised by namespace. Query by meaning or by exact words, and browse by connection in the Hub.
research.papers · research.quotesWorking across vendors
Use one model in one tool and a different one elsewhere; connect both to the same memory store. Shared stores and team roles are not available yet, and accounts and keys are for one person only.
work.notes.decisions · work.notes.runbooksSmall jobs
A one-off fix, a quick analysis, a short script: pay as you go from prepaid credits, with no minimums. Per-minute billing for small jobs is coming soon.
work.jobs.recent · projects.build.notesThe professional practice
Matter notes, procedures and reference material your assistant can find again across sessions and tools. Confidential client data is your responsibility to protect: check your professional obligations and the Privacy Policy before storing it, and verify anything that matters against the original source.
projects.law.cases · projects.law.libraryThe small business
Invoices, reconciliation notes, tax dates and vendor terms. Ask "what did Zeta pay in August" and get back the note you saved, to check against your records. Not tax or accounting advice.
projects.accounting.invoices · projects.businessThe personal life
Goals, taste, routines, the podcast you mentioned. Think carefully before saving sensitive health or financial details, and never rely on memory alone for medication or money decisions.
personal.goals · personal.routines · taste.musicThe household
Home automation preferences, maintenance schedules, warranty receipts and the manual you'll need in eight months.
home.automation · home.maintenanceHow it looks in practice
// you, in any tool connected to your memory: "Remember: Meridian v Zeta hearing is Oct 14, dept 43." // a month later, a different tool connected to the same store: "when is the Meridian hearing?" → projects.law.cases: Meridian v Zeta — hearing Oct 14, dept 43 (score 7.8)
That's the core of it. Everything else (the wiki, the graph, the git history, the file attachments) is your same store, viewed. Retrieval can miss things or return outdated notes, so check anything important against its source.
Across vendors
A vendor's built-in memory stays inside that vendor. Yours doesn't: the store is the same whichever tool or model you connect to it, so switching does not cost you what you've saved.
Less to pay for
Sending only the context a task needs, instead of the whole conversation, used 87.9% fewer tokens on the LoCoMo benchmark (token accounting; your savings depend on your workload). Pay as you go from prepaid credits, or take a monthly coding package with memory included.
Reference libraries
Save reference material you are entitled to use (court rules, tax tables, documentation) into its own namespace, so your assistant can find and quote the saved text. It can still be wrong; check the source.
Start the 7-day trialUse of the service is subject to our Terms of Service and Privacy Policy.