API Overview
The MemoryLake API lets you feed documents and conversations into a project, automatically extract structured facts, and search across all memory sources with natural language. Use it to build AI applications with long-term memory.Base URL
Authentication
All API requests require a Bearer token in theAuthorization header. See Authentication for details.
API Sections
Core Memory Operations
The 3 essential APIs: import documents, append conversation messages, and search memories.
Library
File storage — upload and manage files before importing them into projects.
Workspaces
Create and manage workspaces — the top-level namespace for data isolation.
Actors
Manage participant identities and their associated facts.
Agents
Define AI agents with versioning and A2A protocol support.
Projects
Manage projects and their documents, conversations, and facts.
Common Patterns
Response Format
All responses follow this structure:Your own identifiers
Every resource you create has two identifiers.id is minted here — a prefix and 32 hex characters,
like actor-7b5470549febfaca2acc5a3ebcaa2138. custom_id is the one you bring: the identifier this
thing already has in your system.
Setting it means you do not have to store our id next to your record. Create an actor with the user
id your application already uses, and from then on you can address that actor by it:
A
custom_id must be unique within your tenant, per kind of resource — two actors cannot share
one, though an actor and a project may. Deleting a resource frees its custom_id for reuse.Pagination
List endpoints use continuation-token pagination: Query Parameters:page_size: Number of items per pagecontinuation_token: Token from a previous response to fetch the next page
continuation_token is null, there are no more pages.
Timestamps
All timestamps use ISO 8601 format:Next Steps
Core Memory Operations
Start with the core APIs — see the workflow and prerequisites
Authentication
Set up your API credentials