Skip to main content
Only the base URL, a boundary_id query parameter, and — in BYOK mode — one header. Your prompts, streaming, tool calls, and response handling stay identical, because Memory Router speaks the same API as your provider.
A Boundary is the memory scope for a conversation — it binds requests to a workspace, project(s), and actors so the Router knows whose memory to read and write. You create it once in the console and pass its id as ?boundary_id= on each call. Requests without a boundary_id still work, but pass through with memory disabled.
OpenAI (Chat Completions, Responses, Embeddings) and Anthropic (Messages) protocols. In hosted mode, GPT, Claude, and Qwen model families are built in and callable by their native names. See Deployment Modes for the current matrix.
BYOK (Bring Your Own Key) means you supply your own provider key plus a MemoryLake key — billing and rate limits stay with your provider account. MemoryLake-hosted needs only a MemoryLake key: we run the major models for you, so you skip provider sign-up entirely. Both modes use the same endpoints; the difference is which keys you send.
Yes. Your provider key is encrypted in transit and forwarded to the provider on each call. MemoryLake never stores, logs, or reuses it — the design is stateless, per-request passthrough with zero server-side key storage.
The gateway returns 502 Bad Gateway for that call — retry with backoff, and keep a fallback to a direct provider call if your application requires strict availability. Memory writes are asynchronous, so a slow memory store never delays a successful response. See Observability for the full error contract.
Memory recall happens before the model call and is optimized for low overhead; memory extraction and storage happen asynchronously after the response is returned, so writing memories never adds latency.
Yes. The Router and the MemoryLake API operate on the same memory pool, so anything stored one way is retrievable the other — and visible in the console.
Memory Router is in private preview. If the Memory Router card is not yet visible under Integrations in your console, contact support@memorylake.ai to request access.