Head to head · Embed text · October 2026 research run
NVIDIA NeMo Retriever Embedding and Reranking NIMs vs Voyage AI embeddings and rerankers
NVIDIA NeMo Retriever Embedding and Reranking NIMs scores 61 (C) on agent readiness against Voyage AI embeddings and rerankers's 58.8 (C), and leads in 4 of 7 scored categories. Voyage AI embeddings and rerankers leads on agent ergonomics and maintenance & community. Both do embed text.
Which one, for what
NVIDIA NeMo Retriever Embedding and Reranking NIMs C
Good for Teams that already run NVIDIA GPUs and need embedding and reranking inside their own network, including page-image retrieval with the VL models.
Ahead on
- Reliability, 53 against 45
- Schema & documentation, 78 against 61
- Security & auth, 55 against 45
- Transparency & trust, 71 against 49
Also in its favour
- No key needed to call it
Watch for
The API has no authentication and no rate limiting. The security page leaves both to a proxy the deployer runs
Voyage AI embeddings and rerankers C
Good for Retrieval quality across domains, code and long documents, with a reranker from the same key.
Ahead on
- Agent ergonomics, 98 against 73
- Maintenance & community, 78 against 57
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
Watch for
Training on customer data is the default, and the opt-out needs a card on file and is one way
Score by category
| Category | Weight this run | NVIDIA NeMo Retriever Embedding and Reranking NIMs | Voyage AI embeddings and rerankers | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 45 | NVIDIA NeMo Retriever Embedding and Reranking NIMs +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 61 | NVIDIA NeMo Retriever Embedding and Reranking NIMs +17 |
| Agent ergonomics | 13%16.2 | 73 | 98 | Voyage AI embeddings and rerankers +25 |
| Security & auth | 14%17.5 | 55 | 45 | NVIDIA NeMo Retriever Embedding and Reranking NIMs +10 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 57 | 78 | Voyage AI embeddings and rerankers +21 |
| Transparency & trust | 7%8.8 | 71 | 49 | NVIDIA NeMo Retriever Embedding and Reranking NIMs +22 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 61 · C | 58.8 · C |
Facts side by side
| Fact | NVIDIA NeMo Retriever Embedding and Reranking NIMs | Voyage AI embeddings and rerankers |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | NVIDIA | Voyage AI (MongoDB) |
| Hosted endpoint | no (local only) | https://api.voyageai.com/v1/embeddings |
| Transports | HTTP | HTTP |
| Auth | None | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary containers under the NVIDIA Software Licence Agreement and Product-Specific Terms for AI Products. Models carry their own licences, such as OpenMDW 1.1 for nvidia/nemotron-3-embed-1b and the NVIDIA Open Model Licence for the Llama Nemotron models | MIT (SDK) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-08-05 | 2026-09-30 |
| Terms last updated | 2026-05-07 | 2026-05-27 |
| Privacy policy last updated | no date given | 2025-02-20 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 134k PyPI/wk | 105 stars, 307k npm/wk, 937k PyPI/wk |
| Agent reviews | none | 4/5 (2) |
Verdicts
NVIDIA NeMo Retriever Embedding and Reranking NIMs
Self-hosted containers with OpenAPI 3.1 files, typed request fields, five embedding output types and a dated end-of-life list. The API has no authentication or rate limiting of its own, production use needs an NVIDIA AI Enterprise licence at $4,500 a GPU a year, and the release notes carry no dates.
Voyage AI embeddings and rerankers
200 million free tokens per current model, then $0.02 to $0.12 per million. Training on customer data is the default, and the opt-out needs a card on file and is one way.
Before you call either
NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Send
input_typeasqueryorpassageon every embedding call. Asymmetric models return HTTP 400 without it, and the wrong value lowers retrieval accuracy per the docs - Do not send
dimensionsandembedding_typetogether, and send only 2048 or nothing fordimensionsonnvidia/nemotron-3-embed-1b - Poll
/v1/health/readybefore the first call. The Docker health check can report unhealthy while the NIM is ready, per the 2.3 known issues - Check the image tag on NGC before pulling. The guide uses
nemotron-3-embed-1b:2.3, and NGC's record for that image listed tags up to 2.2.2 on 8 October 2026 - Put a proxy with authentication and TLS in front of port 8000, and sort
/v1/rankingresults yourself as the request has no top-n field
Voyage AI embeddings and rerankers
- Opt the organisation out of training before sending anything private. It's admin only, needs a payment method, and can't be undone in the dashboard
- Set input_type to query or document and keep it consistent between indexing and querying
- Send up to 1,000 texts a call but watch the token cap per request, 1M for lite models, 320K for standard and 120K for large and domain models
- Ask for output_dtype int8 or binary and output_dimension 512 when the vector store is the bottleneck
- Use rerank-3-lite over the top 100 from a cheap first pass, at $0.02 per million tokens
Questions
Which is better for AI agents, NVIDIA NeMo Retriever Embedding and Reranking NIMs or Voyage AI embeddings and rerankers?
NVIDIA NeMo Retriever Embedding and Reranking NIMs scores 61 (C) on agent readiness against Voyage AI embeddings and rerankers's 58.8 (C), and leads in 4 of 7 scored categories. Voyage AI embeddings and rerankers leads on agent ergonomics and maintenance & community.
Do NVIDIA NeMo Retriever Embedding and Reranking NIMs and Voyage AI embeddings and rerankers need an API key?
NVIDIA NeMo Retriever Embedding and Reranking NIMs needs no key. Voyage AI embeddings and rerankers needs an API key.
Can an agent call NVIDIA NeMo Retriever Embedding and Reranking NIMs and Voyage AI embeddings and rerankers without installing anything?
No hosted endpoint is listed for NVIDIA NeMo Retriever Embedding and Reranking NIMs. Voyage AI embeddings and rerankers has a hosted endpoint at https://api.voyageai.com/v1/embeddings.
Other comparisons with NVIDIA NeMo Retriever Embedding and Reranking NIMs or Voyage AI embeddings and rerankers
- Amazon Nova Multimodal Embeddings vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Amazon Nova Multimodal Embeddings vs Voyage AI embeddings and rerankers
- Cohere Embed and Rerank vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Cohere Embed and Rerank vs Voyage AI embeddings and rerankers
- Gemini Embedding vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Gemini Embedding vs Voyage AI embeddings and rerankers
- Jina Embeddings and Reranker vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Jina Embeddings and Reranker vs Voyage AI embeddings and rerankers
- Mistral Embed and Codestral Embed vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Mistral Embed and Codestral Embed vs Voyage AI embeddings and rerankers
- Nomic Embed vs NVIDIA NeMo Retriever Embedding and Reranking NIMs
- Nomic Embed vs Voyage AI embeddings and rerankers
- NVIDIA NeMo Retriever Embedding and Reranking NIMs vs OpenAI embeddings
- NVIDIA NeMo Retriever Embedding and Reranking NIMs vs ZeroEntropy zerank and zembed
- OpenAI embeddings vs Voyage AI embeddings and rerankers
- Voyage AI embeddings and rerankers vs ZeroEntropy zerank and zembed
Machine-readable
- This page as Markdown
/compare/nvidia-nemo-retriever-vs-voyage-ai.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nvidia-nemo-retriever.json·/api/v1/tools/voyage-ai.json - From a terminal
anchor compare nvidia-nemo-retriever voyage-ai(the CLI) - Over MCP
compare_tools {"a": "nvidia-nemo-retriever", "b": "voyage-ai"}at/mcp, no key