Voyage AI Rerank 2

Voyage Rerank 2 is a previous Voyage reranker snapshot, not the live docs lead. Rechecked 2026-08-17: docs.voyageai.com/docs/reranker now leads with rerank-2.5 and rerank-2.5-lite. The same page still lists leftover rerank-2 / rerank-2-lite. Context on the live table is 32K for 2.5 / 2 and 16K for the lite twins, not a 2026 "16k industry lead." Voyage is now under MongoDB. Drop leftover NDCG@10 0.78 / 99.9% SLA / 200-300ms / 3x faster lite as a 2026 census.

Compare text-embedding-3-large if you wanted a still-listed OpenAI retrieval row, and BGE-M3 if you wanted a 2024 open embedding card rather than a billed rerank SKU.

Key Features

• Previous SKU, still listed: rerank-2 remains on the docs table. The headline is 2.5.
• Do not keep 16k as the crown: Live 2.5 / 2 rows say 32K. Lite rows say 16K.
• No invented quality/latency: NDCG 0.78, 200-300ms, and "3x faster" stay off the table unless you re-time a first-party page.
• MongoDB path: Recheck Voyage docs under MongoDB before you quote an independent startup story.

Use Cases

• People with a Rerank 2 bookmark who need the catalog corrected.
• People comparing leftover rerank-2 vs live rerank-2.5.
• People who were about to paste 16k / NDCG 0.78 into a 2026 deck.

Limitation: We did not call rerank-2.5 or re-run BEIR.

Pricing

docs.voyageai.com/docs/pricing on 2026-08-17.

If a leftover blog still calls Rerank 2 the current Voyage default, treat the 2.5 docs as the correction.

Getting Started

1. Open the reranker docs before you hard-code rerank-2.
2. Recheck rerank-2.5 if you wanted the live Voyage path.
3. Recheck the pricing page before you invent a seat or SLA.
4. Do not paste NDCG 0.78 into a deck.

Frequently Asked Questions

Is Rerank 2 still the Voyage default?

No. Docs lead with rerank-2.5.

Is the context 16k?

Not on the live 2.5 / 2 rows. Those say 32K. Lite says 16K.

Same as Voyage 3 Large?

No. voyage-3-large is an embedding snapshot. This slug is a leftover rerank SKU.

Alternatives

• voyage-3-large: Voyage embedding snapshot on this site.
• text-embedding-3-large: Still-listed OpenAI v3 retrieval row.
• BGE-M3: 2024 open multilingual embedding card.

Tips

1. Call Rerank 2 a previous snapshot that is still priced.
2. Point new Voyage rerank work at rerank-2.5.
3. Recheck MongoDB / Voyage docs before you invent an SLA.

Conclusion

Voyage Rerank 2 is a previous snapshot still on the pricing table, not the 2026 Voyage rerank default. Start at docs.voyageai.com/docs/reranker, then decide whether rerank-2.5 already covers the path you need.