BYOK — Bring Your Own Key
Use your own provider account. Your provider key is encrypted in transit, forwarded to the provider per call, and never stored on our servers.- Keep your existing OpenAI / Anthropic / Google account.
- Your key, your billing, your rate limits.
- Key is encrypted + passthrough only — never persisted or logged.
https://router.memorylake.ai/v1/openai
Keys: your provider key (as the SDK API key) + MemoryLake key (as the x-memorylake-api-key header)
TypeScript
MemoryLake-hosted
No provider account required. MemoryLake runs the major models for you, so a single MemoryLake API key is all you need to start.- One key for everything — nothing else to sign up for.
- Mainstream models built in and ready to call.
- The simplest possible way to ship with memory.
https://router.memorylake.ai/v1
Keys: MemoryLake key only
TypeScript
Choosing a Mode
| BYOK | MemoryLake-hosted | |
|---|---|---|
| Provider account | Required (yours) | Not required |
| Keys | Provider key + MemoryLake key | MemoryLake key only |
| Billing & rate limits | Stay with your provider account | Handled by MemoryLake |
| Base URL | …/v1/openai | …/v1 |
| Best for | Teams with existing provider contracts and quotas | Fastest path to ship with memory |
Key Safety, by Design
Supported Providers
In BYOK mode, keep your provider account and key. In hosted mode, MemoryLake runs these models for you — the same memory layer either way.| Provider | Status |
|---|---|
| OpenAI / GPT | Fully supported |
| Anthropic / Claude | Fully supported |
| Google Gemini | Fully supported |
| Groq, DeepSeek, OpenRouter | Fully supported |
| Any OpenAI-compatible endpoint | Supported |
| OpenAI Assistants API | Not yet supported |
Next Steps
Quickstart
Copy-paste setup for both modes.
Observability
Confirm behavior with diagnostic response headers.