How to choose the model that writes your memories

@mem0ai
mem0@mem0ai
16 views Oct 28, 2026 ~5 min read
Advertisement

Every add request to Mem0 runs a language model. It reads the conversation and decides what to keep: a user’s preferences, a deadline, a change of plans. With bring your own key (BYOK), you can pick that model.

Media image

The model choice impacts three numbers:

  • how accurate your memories are
  • what each add request costs
  • how soon a new memory can be found
  • We ran 17 models through the same benchmark to see how each performs with the Mem0 algorithm, and naturally, the spread is quite wide. The least accurate model misses 2.4 times as many questions as the most accurate. The most expensive costs 233 times as much as the cheapest.

    This article covers what BYOK gives you, which providers it works with, and how to decide whether a model fits your use case.

    What BYOK gives you

  • You choose the trade-off. A companion app that engages with users for years needs different memories than a support bot that answers one-off tickets.
  • Your code stays the same. Add and search calls don’t change. Only the underlying model that extracts memories changes.
  • Your data goes through your own provider. If your security review already approved a provider, the memory layer uses the same one.
  • Model calls bill to your provider account. You can use credits, committed spend or discounts you already have with OpenAI, Anthropic or Azure.
  • BYOK works with four providers: OpenAI, Anthropic, Azure OpenAI and OpenRouter. OpenRouter carries every model we tested, including open-weight models such as DeepSeek, GLM, Gemma and Mistral, and the Google and Amazon models.

    What we measured

    We ran every model on LoCoMo, a public benchmark of 10 long conversations and 1,540 questions about them, and recorded three numbers:

  • Accuracy: how often a question about a past conversation is answered correctly from the memories the model wrote.
  • Cost: what the provider bills for 1,000 add requests. Each request in the test carried about 8 messages, so larger requests cost more.
  • Latency: the time from an add request until its memories can be found; at p95, 19 of every 20 requests finish within that time.
  • Accuracy ranged from 84.1% to 93.5%. Cost ranged from $0.68 to $158.55 per 1,000 add requests. Latency ranged from 6.1 to 86.5 seconds. Mem0’s default setup scores 92.5%.

    Five questions to pick a model

    1. How much does a missed memory cost you?

    Start with what a wrong or missing memory does to your product. If your app tracks health details, long-running goals or account history, one missed fact can lose a user’s trust. If memories only make replies a little more personal, a miss costs less.

    At 93.5%, the best model misses about 1 question in 15. At 84.1%, the weakest misses about 1 in 6. Six models score above Mem0’s default: Claude Opus 5.5, Claude Sonnet 5.5, GLM-5.3 Flash, DeepSeek V4.1 Flash, GPT-6 Luna and GPT-5 mini.

    The top of the range is flat. Claude Opus 5.5 scores only 0.6 points above DeepSeek V4.1 Flash and costs about 30 times as much. Claude Sonnet 5.5 scores within 0.1 points of Opus at half the price. If accuracy comes first, the last point costs much more than the ones before it.

    2. What does it cost at your volume?

    Multiply the price per 1,000 add requests by your monthly volume. At 100,000 add requests a month:

    ModelAccuracyA month at 100K adds
    Amazon Nova Micro88.0%$86
    GPT-6 Luna92.6%$355
    Claude Haiku 5.592.3%$493
    DeepSeek V4.1 Flash92.9%$534
    GPT-5 mini92.6%$1,782
    Claude Sonnet 5.593.4%$7,844
    Claude Opus 5.593.5%$15,855

    At high volume, the cheap end matters. Amazon Nova Micro is the most accurate model under $1 per 1,000 add requests among our test set. Amazon Nova Lite adds 1.3 points for about twice the price.

    3. How soon does a new memory need to be findable?

    Mem0 extraction runs asynchronously so that a slow model won't delay your app’s reply. But a new memory can’t be found until it’s written.

    If your users refer back to something they said a few messages earlier, choose a fast model. Among the models above Mem0’s default setup, Claude Sonnet 5.5 (10.4 s) and GPT-6 Luna (15.2 s) are the fastest. Models that reason before they write are slower: Gemini 3.8 Flash takes 36.0 s, GPT-5 mini 37.7 s and GLM-5.3 Flash 86.5 s.

    If your app only reads memories in the next session, latency doesn't matter as much.

    4. Which provider are you already on?

  • OpenAI or Azure OpenAI: choose GPT-6 Luna. It matches GPT-5 mini’s 92.6% at a fifth of the cost, $3.55 against $17.82 per 1,000 add requests, and finishes more than twice as fast.
  • Anthropic: choose Claude Sonnet 5.5 or Opus 5.5 if accuracy comes first. Choose Claude Haiku 5.5 if cost does; it scores 92.3% for $4.93.
  • OpenRouter: every model in the test is there. DeepSeek V4.1 Flash is the best value overall at 92.9% for $5.34.
  • 5. Does it hold up on your own conversations?

    LoCoMo is long, casual chat between two people. Your traffic may look different: short support tickets, health check-ins or several languages. Treat the benchmark as a suggestive shortlist, then test the shortlist on your own data.

  • Pick two or three candidates from the questions above.
  • Set up a test organization on Mem0, since the key is set per organization.
  • Replay 50 to 100 real conversations for each model. Give each model its own user_id, so the memories stay separate.
  • Ask the questions your app actually asks before a reply. Compare the answers.
  • Check your provider’s usage page for the real cost per request at your message length.
  • Our picks

    If you care most aboutChooseAccuracy$/1K addsp95
    Value, on any providerDeepSeek V4.1 Flash92.9%$5.3418.5 s
    Cost, under $1Amazon Nova Micro88.0%$0.8610.2 s
    Accuracy and speedClaude Sonnet 5.593.4%$78.4410.4 s
    Staying on OpenAIGPT-6 Luna92.6%$3.5515.2 s
    Staying on Anthropic, cost firstClaude Haiku 5.592.3%$4.9317.7 s

    Setting it up

    An organization owner can go to Settings > BYOK, pick the provider and the model, and paste the API key. From then on, Mem0 extracts memories with that model and bills the calls to your key. Your Mem0 integration code stays the same.

  • The full results, with all tested models and an interactive cost calculator, are in our blog post: https://mem0.ai/blog/bring-your-own-key-accuracy-cost-latency-by-model
  • Setup guide: https://docs.mem0.ai/platform/features/byok
  • Mem0 App: https://app.mem0.ai
  • If you run your own comparison and get different numbers on your data, we want to hear about it.

    Written by: @Rudrajmehta, Product, Mem0

    Actions
    What You Can Do
    • Export as PDF or Markdown
    • Batch Export to Notion
    • Bookmark & Highlight
    • Screenshot Tweet
    Create Free Account

    Includes 7-day Premium trial

    Advertisement