diff --git a/docs/docs.json b/docs/docs.json
index 4371c1ffe..ea291d1e0 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -87,7 +87,8 @@
"platform/advanced-memory-operations",
"platform/features/custom-instructions",
"platform/features/memory-decay",
- "platform/features/dream"
+ "platform/features/dream",
+ "platform/features/byok-models"
]
},
{
diff --git a/docs/images/platform/byok-accuracy-vs-cost.png b/docs/images/platform/byok-accuracy-vs-cost.png
new file mode 100644
index 000000000..020c40fc0
Binary files /dev/null and b/docs/images/platform/byok-accuracy-vs-cost.png differ
diff --git a/docs/images/platform/byok-picks.png b/docs/images/platform/byok-picks.png
new file mode 100644
index 000000000..f09b9b2af
Binary files /dev/null and b/docs/images/platform/byok-picks.png differ
diff --git a/docs/llms.txt b/docs/llms.txt
index c511033ce..b387a8677 100644
--- a/docs/llms.txt
+++ b/docs/llms.txt
@@ -209,6 +209,7 @@ If the user is on a pre-current major (Python < 2, TS < 3, or a Platform call st
- [Custom Instructions](https://docs.mem0.ai/platform/features/custom-instructions) [Platform]: Use when tailoring what Mem0 extracts and stores on Platform.
- [Memory Decay](https://docs.mem0.ai/platform/features/memory-decay) [Platform]: Use when search results should boost recently-reinforced memories and dampen stale ones. Opt in per project; applies at search time and never filters candidates out.
- [Dream](https://docs.mem0.ai/platform/features/dream) [Platform]: Use when long-lived user memory should stay coherent on its own - synthesizing recurring patterns, superseding outdated facts, and merging duplicates in the background. Synthesis is opt-in (Pro+); Supersede and Merge are always on.
+- [Choosing a Model for BYOK](https://docs.mem0.ai/platform/features/byok-models) [Platform]: Use when choosing which LLM writes memories on your own key (BYOK) - accuracy, cost per 1,000 adds and latency for each model, plus setup.
- [Advanced Memory Operations](https://docs.mem0.ai/platform/advanced-memory-operations) [Platform]: Use when basic CRUD is not enough - batch ops, complex filters, workflows.
### Features - Data Management
diff --git a/docs/platform/features/byok-models.mdx b/docs/platform/features/byok-models.mdx
new file mode 100644
index 000000000..c29896b7f
--- /dev/null
+++ b/docs/platform/features/byok-models.mdx
@@ -0,0 +1,70 @@
+---
+title: "Choosing a Model for BYOK"
+description: "Compare models for BYOK on accuracy, cost and latency, and pick the right one for your use case."
+icon: "key"
+---
+
+With BYOK, memory extraction runs on a model you choose, billed to your own key. On [LoCoMo](https://github.com/snap-research/locomo), a public benchmark of 10 long conversations and 1,540 questions about them, we tested the most used, most capable and cheapest well-known models that work with BYOK, open-weight and closed. The results below show how accurate each model's memories are, what they cost and how long extraction takes.
+
+
+ **Read more:** a calculator for your monthly volume is in the [full evaluation](https://mem0.ai/blog/bring-your-own-key-accuracy-cost-latency-by-model).
+
+
+## Which model to use
+
+Each pick serves a different goal: **Best value** balances accuracy and price, **Best under $1** is the most accurate model under $1 per 1,000 add requests and **Best quality** the highest accuracy.
+
+
+
+
+
+## Results
+
+Accuracy against cost for every model we tested. The green line marks the best accuracy available at each price, the gold area holds the models under $2 per 1,000 add requests, and the gray dashed line is Mem0's default model, at 92.5%.
+
+
+
+
+
+Every model we tested, sorted by accuracy:
+
+| Model | Accuracy | $ per 1,000 add requests | Latency p95 |
+|---|---|---|---|
+| Claude Opus 5.5 | 93.5% | $158.55 | 18.1 s |
+| Claude Sonnet 5.5 | 93.4% | $78.44 | 10.4 s |
+| GLM-5.3 Flash | 93.0% | $7.25 | 86.5 s |
+| DeepSeek V4.1 Flash | 92.9% | $5.34 | 18.5 s |
+| GPT-6 Luna | 92.6% | $3.55 | 15.2 s |
+| GPT-5 mini | 92.6% | $17.82 | 37.7 s |
+| Claude Haiku 5.5 | 92.3% | $4.93 | 17.7 s |
+| Gemini 3.8 Flash | 92.0% | $48.08 | 36.0 s |
+| GPT-5.4 nano | 91.6% | $6.06 | 9.9 s |
+| GPT-4o-mini | 91.3% | $4.25 | 11.9 s |
+| Gemma 4 31B | 90.6% | $3.57 | 18.5 s |
+| Gemini 3.5 Flash-Lite | 89.9% | $7.08 | 6.1 s |
+| Amazon Nova Lite | 89.3% | $1.82 | 9.3 s |
+| Amazon Nova Micro | 88.0% | $0.86 | 10.2 s |
+| Gemma 3 4B | 86.8% | $1.19 | 19.6 s |
+| GPT-4.1 nano | 85.5% | $1.54 | 15.9 s |
+| Mistral Nemo | 84.1% | $0.68 | 9.8 s |
+
+Every model is available on OpenRouter; the GPT models are also on OpenAI and Azure OpenAI, and the Claude models on Anthropic.
+
+## Set up BYOK
+
+1. As an organization owner, open **Settings → BYOK** in the [Mem0 dashboard](https://app.mem0.ai/dashboard/settings?tab=org-llm).
+2. Pick a provider: OpenAI, Anthropic, OpenRouter or Azure OpenAI.
+3. Paste your API key and enter the model. On OpenRouter, use the model's full ID, such as `deepseek/deepseek-v4.1-flash`. Azure OpenAI also needs your endpoint URL and deployment name.
+4. Click **Save provider**. Mem0 extracts your memories with that model from then on. **Disable provider** switches back to Mem0's default model.
+
+## How we tested
+
+- Every model took the same test, and only the model extracting memories changed.
+- Accuracy is the share of LoCoMo's questions answered correctly from each model's memories, graded against LoCoMo's reference answers and averaged over two runs.
+- Cost is estimated from each model's calls, per 1,000 add requests of about 8 messages each.
+- Latency is the p95 time from an add request until its memories can be found: 19 of every 20 requests finish within that time. It also depends on your provider and plan.
+- Results from October 2026.
+
+
+ Every model's accuracy, cost and latency, and a calculator for your monthly volume.
+