You don’t need to set any of this up by hand. When you sign up, MemoryLake automatically provisions a workspace and assistant for you — these concepts become useful as your usage grows from “my personal memory” to “my team’s memory” to “memory inside my product.”
The Hierarchy
Workspaces & Projects
Isolation boundaries, knowledge containers, and multi-tenant patterns.
Actors & Memory
Identities, project facts vs. actor facts, and per-user memory.
Memory Pipeline
How documents and conversations become searchable memory.
Individual Memory and Organizational Memory
The same machinery serves two different kinds of knowledge, and knowing which you’re building matters more than any API detail.
Both flow through the same pipeline — extraction, source traces, conflict checking, retrieval. The difference is scope and governance. See the Personal AI Memory and Team Knowledge Base scenarios.
Memory Hygiene: Traces and Conflicts
Two properties make memory trustworthy enough to build on:- Source traces — every memory links back to the conversation or document it came from. When an assistant asserts something, you can always answer “how do you know that?” Available in the console and via the trace API.
- Conflict detection — when a new memory contradicts an existing one (a moved deadline, a changed policy), MemoryLake flags a conflict for review instead of silently keeping both. In teams, whoever holds the resolve permission decides what’s true.
Open Data
Open Data is curated external knowledge you subscribe a project to — research and academic sources, clinical trials, drug databases, financial markets, company fundamentals, economic indicators, patents, and more. Subscribed categories become searchable by agents alongside your own content, so a biotech project can cite PubMed while a fintech project cites SEC filings.Boundary (Memory Router & MCP)
A boundary is the memory scope used by API traffic and MCP clients. It binds a workspace, project(s), and actors into a single reference:- With Memory Router, you pass it as
?boundary_id=on LLM calls — commonly one boundary per end user, so each user’s conversations read and write only their own memory. - With MCP, you select the workspace and boundary on the OAuth consent screen when a client connects.
API Key
An API key (sk-…) is your credential for everything programmatic: the REST API, Model Router, and agent plugins. Create keys in the console under API Keys — each has a name and an expiry, and its permissions mirror those of the member who created it. Rotate or revoke anytime. See Authentication.
How the Concepts Map to You
Quick Start
Experience memory in the console in five minutes.
Scenarios
Deep-dive walkthroughs for personal, team, agent, and product use cases.