[Blog](https://supermemory.ai/blog) · [Learning](https://supermemory.ai/blog/tag/learning)

# Choosing Embedding APIs for Production Retrieval

Compare embedding providers by supported inputs, retrieval quality, compatibility and workload cost. Keep embedding APIs separate from databases and memory services.

By Shardul Mane April 17, 2026 · 5 min read 

![Embedding APIs for production AI](https://supermemory.ai/_astro/cover.Q07yzjLY_ZrdPf2.webp)

Choose an embedding API by the representation your retrieval workload needs. An embedding endpoint returns vectors. A vector database stores and searches records. A memory service adds behavior around retained context. They can be combined, but a memory benchmark is not an embedding-model leaderboard.

The options below cover text, code and multimodal representations. Use the evaluation method to compare them on your documents and queries.

## Define the input and output contract

Record supported modalities, input limits, query/document instructions, output dimensions and data types. A text embedding model does not automatically accept a PDF file simply because text can be extracted from that PDF.

Likewise, a large input limit does not mean every document should become one vector. A long document covering several topics may need smaller searchable units for precise answers. Compare evidence coverage using the [chunking guide](https://supermemory.ai/blog/text-chunking-strategies-for-rag/).

## OpenAI text embeddings

[OpenAI's embedding guide](https://developers.openai.com/api/docs/guides/embeddings) documents `text-embedding-3-small` and `text-embedding-3-large`, including configurable output dimensions. Their default dimensions are 1,536 and 3,072 respectively.

Evaluate those text-embedding endpoints for the languages and tasks you actually serve. Keep query and document preprocessing consistent when comparing them.

Follow the selected model's limits and pricing. Do not equate a smaller vector with an identical reduction in encoding cost or guaranteed unchanged recall.

## Voyage embeddings

[Voyage's model table](https://docs.voyageai.com/docs/embeddings) distinguishes general-purpose, code, finance and legal models. For example, the listed Voyage 4 general-purpose models have a 32,000-token context length and support several output dimensions. The legal model has a different limit; do not apply one row's specifications to every model.

Use the documented query and document input types where appropriate. Test domain-specific candidates on your own corpus instead of assuming a domain label proves superiority. Multimodal models have a separate input contract that should be evaluated directly for image or video workloads.

## Cohere embeddings

[Cohere's Embed documentation](https://docs.cohere.com/docs/cohere-embed) covers embedding models and their supported text or multimodal inputs. Check the specific model, dimension choices and output types rather than treating every Cohere embedding endpoint as interchangeable.

For visually rich source material, evaluate whether the representation retains the information needed for the question. A page containing a chart requires different evidence checks from plain prose. Larger input limits can reduce some preprocessing constraints, but they do not eliminate the need to select useful retrieval units.

## Database integrations are a separate choice

[Weaviate's model-provider integrations](https://docs.weaviate.io/weaviate/model-providers) can generate vectors through configured providers.

Pinecone also documents [integrated embedding](https://docs.pinecone.io/guides/index-data/indexing-overview). Confirm which service performs encoding, where data is sent and how the charges appear. A database integration changes who invokes the model; it does not remove the model's compatibility and quality constraints.

Supermemory's [search API](https://supermemory.ai/docs/recall/search) is evaluated as part of a memory/retrieval service. Evaluate its returned evidence and answers separately from the raw embedding models you might use in a custom stack.

## Build a comparison that matches production

Use representative documents and questions, including exact identifiers, paraphrases, rare terms, changed documents and missing answers. Label acceptable supporting passages before comparing models.

Keep corpus revisions, access filters, chunking and candidate budgets fixed. Change one major component at a time. If a model requires different preprocessing, record that difference rather than hiding it in an otherwise identical-looking result table.

Measure:

* Whether supporting evidence appears within the selected candidate set.
* Whether the final answer uses that evidence correctly.
* Query encoding and retrieval latency separately.
* Rate-limit errors and retry volume under expected concurrency.
* Ingestion, storage and serving costs for the same workload.

MTEB results can help identify candidates, but select the relevant tasks and benchmark revision. They do not establish API availability or p99 latency under your traffic.

## Calculate raw vector storage

One million float32 vectors at 1,536 dimensions contain 6.144 decimal GB of raw values. At 3,072 dimensions they contain 12.288 GB. Index structures, metadata, source content, replicas and backups add to those figures.

Reducing dimensions can lower raw-vector storage, but retrieval quality must be tested. The [Matryoshka guide](https://supermemory.ai/blog/matryoshka-representation-learning-the-ultimate-guide-how-we-use-it/) explains why supported shorter representations differ from arbitrarily truncating any embedding.

For pricing, estimate new and changed source tokens, query volume, retries and re-embedding. Add storage and reranking if they are part of the chosen system.

## Plan model changes before they happen

Pin model identifiers and preprocessing where possible. Two models producing the same number of dimensions are not automatically compatible. If changing representations, evaluate a parallel index and cut over only after the new path passes the acceptance cases.

Preserve source IDs and revisions so reprocessing can target the intended documents. A rollback should restore a compatible query model and index together; changing only one side can silently damage retrieval.

## Decide which layer you want to operate

Choose an embedding API when you need control over representations and already have, or want to build, the surrounding retrieval path. Choose a database integration when it provides the controls you need with less encoding orchestration. Evaluate a memory service when persistent context, ingestion and lifecycle behavior are the larger requirement.

[Try Supermemory alongside your retrieval baseline](https://console.supermemory.ai/) if that last requirement applies. Compare the complete answers and operating work, while keeping the embedding-model experiment a separate, reproducible decision.

## Frequently asked questions

### Which measurements help compare embedding APIs?

Compare evidence recall, query-encoding latency, error rates and cost on the same corpus and question set. Use relevant embedding-benchmark tasks to identify candidates for that evaluation.

### Does a longer embedding input limit remove the need for chunking?

No. Smaller units may still be necessary for precise evidence retrieval. Test the document types and questions you need to answer.

### Does Weaviate require manually generated vectors?

No. It supports configured model-provider integrations as well as supplied vectors. Check the selected integration and its data flow.

## Other posts.

1. [We're open sourcing the company brain. Here's how we designed the multiplayer harness Company Brain is now open source. A walkthrough of the multiplayer harness behind its Slack experience, from proactivity and memory boundaries to approvals and recovery. NewsSep 25, 2026 ](https://supermemory.ai/blog/open-sourcing-company-brain)
2. [Jev changes a lot in memory & context engineering. Here's exactly how. We tested Jev across reranking, chunking, observation, and harness decisions. Here is where fast decision models help memory systems, where they cost more, and where they still fall short. EngineeringSep 24, 2026 ](https://supermemory.ai/blog/jev-memory-context-engineering)
3. [I reverse-engineered Instinct's memory. Here's exactly how it works Instinct keeps its memory as git-tracked markdown files, found with grep rather than vectors. Here is the whole system as far as black-box probing can reconstruct it, and how to rebuild it on supermemory in about 60 lines. EngineeringSep 20, 2026 ](https://supermemory.ai/blog/reverse-engineering-instinct-memory)
4. [An update to supermemory We've discontinued the supermemory company brain and Nova. Everyone who was charged has been refunded, our MCP and plugins continue to run, and we're going all in on the memory engine. NewsSep 10, 2026 ](https://supermemory.ai/blog/an-update-to-supermemory)
5. [Scaling Conversations: How Adapta Grew Usage Without Losing Context Adapta added Supermemory as a persistent memory layer so every conversation keeps its context — letting the team scale usage without losing the thread. Case StudyJun 12, 2026 ](https://supermemory.ai/blog/adapta-scaling-conversations)
6. [How Chatarmin Ditched RAG and Went Memory-Only with Supermemory Chatarmin replaced a heavy RAG pipeline with Supermemory's memory layer — cutting average AI response time from 40s to 12s and token usage by 40–50%. Case StudyJun 10, 2026 ](https://supermemory.ai/blog/chatarmin-memory-only)
7. [SMFS: making agentic retrieval 55% cheaper AND more accurate We launched SMFS.ai (Supermemory Filesystem) a few weeks ago, with a simple bet: We can redesign the filesystem specifically for agents, with special files, structures, and commands that it can use for it's tasks. Today, SMFS is used by hundreds of companies to power their agents. EngineeringMay 28, 2026 ](https://supermemory.ai/blog/smfs-making-agentic-retrieval-55-cheaper-and-more-accurate)
8. [Introducing Dynamic Dreaming: supermemory now connects the dots, for you. Dreaming is magical. TLDR: We're launching Dynamic Dreaming in supermemory today, which automatically works if you're using supermemory in any way - API, OpenClaw, Hermes agent, etc. EngineeringMay 25, 2026 ](https://supermemory.ai/blog/introducing-dynamic-dreaming-supermemory-now-connects-the-dots-for-you)
9. [Dear reader, we just made supermemory insanely cheap... the Context Cloud When I first started building supermemory, I had one goal: To build the best memory system for AI. I would talk to customers, and find out that memory was not the only thing they needed - They were all setting up 7-8 different vendors at the same time. EngineeringMay 18, 2026 ](https://supermemory.ai/blog/dear-reader-we-just-made-supermemory-insanely-cheap-the-context-cloud)
10. [Introducing @supermemory/tools v2.0.0 Today we're releasing v2.0.0\. This release unifies the API across all agents sdk integrations from AI SDK to Mastra, makes conversation identity a first-class concept, and ships with memory saving on by default. EngineeringApr 27, 2026 ](https://supermemory.ai/blog/introducing-supermemory-tools-v2-0-0)
11. [Solving the Precision-Recall Tradeoff: Search Result Aggregation When you're building memory for AI, search is your foundational layer. The way search generally works is straightforward: the user defines a query, and then sets a limit (top-K) on how many search results they want returned. Usually, this is set to 10 or 20. EngineeringApr 5, 2026 ](https://supermemory.ai/blog/solving-the-precision-recall-tradeoff-search-result-aggregation)
12. [OpenClaw Memory Problems: Why It Forgets and How to Fix It (2026) TLDR: Today, we are releasing a new version of our openclaw plugin - https://github.com/supermemoryai/openclaw-supermemory. This post is going to be a bit technical, so bear with me (or bookmark for later!) In this post, I will talk about what we do about OpenClaw memory, and how we fix it. EngineeringFeb 19, 2026 ](https://supermemory.ai/blog/why-everyone-is-complaining-about-openclaws-memory-it-sucks-and-why-supermemory-fixes-it)
13. [Stateful Coding Agents with Memory: Build Long-Running Agents (2026) We built a plugin for Claude Code and OpenCode that gives your coding agent persistent memory. It remembers your preferences, learns your codebase, and never loses context mid-conversation. The result is an agent you can run for months without starting over. EngineeringFeb 18, 2026 ](https://supermemory.ai/blog/infinitely-running-stateful-coding-agents)
14. [Clawd / Molt bot's memory SUCKS. We gave it supermemory. I'm the founder of supermemory. Clawd/Molt bot is blowing up right now, with many, many use cases. I set it up, too, and have been using it through telegram. TLDR: just go to https://supermemory.ai/docs/integrations/clawdbot to set up supermemory for your clawd bot. EngineeringJan 28, 2026 ](https://supermemory.ai/blog/clawd-molt-bots-memory-sucks-we-gave-it-supermemory)
15. [Catch up with our UNFORGETTABLE Launch Week Over the last year, one belief has guided almost everything we’ve built at Supermemory AI becomes meaningfully useful only when it remembers. Memory shouldn’t be something developers rebuild from scratch. It shouldn’t be fragile, expensive, or trapped inside a single tool. NewsJan 4, 2026 ](https://supermemory.ai/blog/catch-up-with-our-unforgettable-launch-week)
16. [Empowering the Next Generation of Founders: Supermemory Startup Program If there’s one thing we’ve learned while building Supermemory, it’s that most startups don’t fail because they didn't build features; they fail when infrastructure slows them down, or they built too slow. NewsDec 31, 2025 ](https://supermemory.ai/blog/empowering-the-next-generation-of-founders-supermemory-startup-program)
17. [Building code-chunk: AST Aware Code Chunking At Supermemory, we're building context engineering infrastructure for AI. A huge part of that is dealing with code: ingesting repos, understanding structure, and making it searchable. The problem is that most code chunking solutions are terrible. We built code-chunk to fix this. EngineeringDec 29, 2025 ](https://supermemory.ai/blog/building-code-chunk-ast-aware-code-chunking)
18. [Supermemory raises $3 million with the best memory engine for LLMs Today, I am excited to announce our first funding round to accelerate our mission of building an interoperable, scalable and reliable memory for LLMs and agents. Memory is one of the hardest challenges in AI right now. NewsOct 6, 2025 ](https://supermemory.ai/blog/supermemory-raises-3-million-and-building-the-best-memory-engine-for-llms)
19. [Mem0 vs Supermemory: Why Scira Switched Scira AI moved its production memory layer from Mem0 to Supermemory. This is what failed, what improved, and how the team evaluated the two systems. Case StudyOct 2, 2025 ](https://supermemory.ai/blog/why-scira-ai-switched)
20. [Never Record Again: How Montra Uses Supermemory to Rethink Video Creation Campbell Baron, the founder of Montra, has been making videos since he was twelve. By thirteen, he was already doing brand work. Today, he’s betting on a very different future for creators: a world where recording is the exception, and most videos are generated from scratch. Case StudyAug 21, 2025 ](https://supermemory.ai/blog/never-record-again-how-montra-uses-supermemory-to-rethink-video-creation)
21. [Unified Memory That Works Where You Work: Your Second Brain With Supermemory Hi everyone, I’m Dhravya, the founder of Supermemory. I want to start with a little story behind why this product means so much to me. You can also skip straight to what it is and how it works below. EngineeringJul 25, 2025 ](https://supermemory.ai/blog/unified-memory-that-works-where-you-work-your-second-brain-with-supermemory)
22. [Supermemory just got faster on PlanetScale What is Supermemory? Supermemory completes the missing part of the LLM puzzle: memory. Just as memory is crucial for human intelligence, it's essential for truly intelligent AI systems. EngineeringJul 18, 2025 ](https://supermemory.ai/blog/supermemory-just-got-faster-on-planetscale)
23. [Faster, smarter, reliable infinite chat: Supermemory IS context engineering. People are obsessed with prompts and prompt engineering. Sure, what you say is important, but what the model knows when you say it is the difference between a stateless text generator and an intelligent AI system. In short, context is the most crucial component. NewsJul 9, 2025 ](https://supermemory.ai/blog/faster-smarter-reliable-infinite-chat-supermemory-is-context-engineering)
24. [We solved AI API interoperability One API to rule them all, One spec to find them, One library to bring them all and in the TypeScript, bind them. When we were building the Infinite Chat API, initially, we only supported the OpenAI format. This was fine, until a lot of our customers started asking for more. EngineeringJul 7, 2025 ](https://supermemory.ai/blog/we-solved-ai-api-interoperability)
25. [The Wow Factor of Memory - How Flow Used Supermemory To Build Smarter, Stickier Products Overview: Flow is a note-taking app built around a bold vision: to create a more personal, context-aware writing experience powered by AI. At the heart of this mission is memory. Case StudyJun 14, 2025 ](https://supermemory.ai/blog/the-wow-factor-of-memory-how-flow-used-supermemory-to-build-smarter-stickier-products)
26. [The UX and technicalities of awesome MCPs Last month, we launched the Supermemory MCP, mostly to test our own infrastructure and get some initial traction. It blew up. To my absolute surprise, the initial launch itself got half a million impressions (!!!). Then, we launched and got #2 on ProductHunt too. EngineeringJun 8, 2025 ](https://supermemory.ai/blog/the-ux-and-technicalities-of-awesome-mcps)
27. [Architecting a memory engine inspired by the human brain Language is at the heart of intelligence, but what truly powers meaningful interaction is memory — the ability to accumulate, recall, and contextualize information over time. Large Language Models (LLMs) have mastered language, but memory remains their Achilles’ heel. EngineeringJun 5, 2025 ](https://supermemory.ai/blog/memory-engine)

## Start building with supermemory.

Memory and continual learning for any model, any harness. Available through our API, plugins, and MCP.

[Build with supermemory ](https://console.supermemory.ai/)