Voyage 4 Lite
Voyage 4 Lite is the lightweight Voyage 4 model. Voyage AI by MongoDB reports it approaches voyage-3.5 retrieval accuracy with fewer parameters, shares one embedding space with voyage-4-large and voyage-4, and supports a context window of 32K tokens with Matryoshka dimensions and quantization like the rest of the family.
- Input price
- Input $0.02, Per 1M tokens
import { embed } from 'ai';
const result = await embed({ model: 'voyage/voyage-4-lite', value: 'Sunny day at the beach',})Copy link to headingProviders
Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.
| Provider |
|---|
| 32K | $0.02/M | 01/15/2026 |
Copy link to headingMore models by Voyage AI by MongoDB
| Model |
|---|
| 32K | $0.06/M | — |  | 01/15/2026 | ||||||||||
| 32K | $0.12/M | — | | 01/15/2026 | ||||||||||
| 32K | $0.02/M | — | | 08/11/2025 | ||||||||||
| 32K | $0.05/M | — | | 08/11/2025 | ||||||||||
| — | $0.02/M | — | | 05/20/2025 | ||||||||||
| — | $0.18/M | — | | 01/07/2025 |
Copy link to headingAbout Voyage 4 Lite
Voyage 4 Lite strips down the Voyage 4 architecture to fewer parameters, released January 15, 2026. The result is a model that processes tokens faster and cheaper than its siblings while retaining enough retrieval quality for most production use cases.
Voyage AI by MongoDB benchmarks Voyage 4 Lite near voyage-3.5 retrieval accuracy. For teams running millions of daily requests or indexing large corpora on a budget, the per-token savings add up fast. Development and staging environments also benefit: cheaper iteration cycles let you experiment with chunking strategies and retrieval pipelines without burning through credits.
Because all Voyage 4 models produce compatible vectors, you aren't locked into Voyage 4 Lite for every step of your pipeline. Index your corpus with a stronger variant, then point live traffic at Voyage 4 Lite for lower query costs. No re-indexing required.
Copy link to headingWhat To Consider When Choosing a Provider
- Configuration: Use Voyage 4 Lite for queries when
voyage-4-largealready holds your document vectors, or as a budget option when both sides use the same model and your accuracy targets match Voyage AI by MongoDB's voyage-3.5 positioning. Plan a full re-embed when moving into Voyage 4, and test on a sample before indexing the full corpus. - Zero Data Retention: Zero Data Retention is offered on a per-provider and model basis. See the documentation for details.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
Copy link to headingWhen to Use Voyage 4 Lite
Best for
- High query traffic: Pair Voyage 4 Lite queries with
voyage-4-largedocument embeddings to keep per-query cost low without re-indexing - Cost-sensitive symmetric indexing: Voyage 4 Lite on both sides when voyage-3.5-level retrieval accuracy is sufficient and per-token cost drives the decision
- Early production and prototypes: Iterate cheaply before upgrading query-side models once traffic patterns stabilize
- Batch jobs: Large-corpus indexing runs where per-token cost compounds across millions of requests
Consider alternatives when
- Higher published average scores: Use
voyage-4-largeorvoyage-4when retrieval accuracy matters more than per-token cost - Code-only corpora: Use
voyage-code-3for repositories where source code is the primary content type - Multimodal embeddings: Use a model with native image inputs when you need to embed diagrams, screenshots, or mixed-format documents
Copy link to headingConclusion
Pick Voyage 4 Lite when your embedding bill scales with request volume and you need Voyage 4 generation quality at the tightest possible price point. Route through AI Gateway to swap between Voyage 4 tiers without changing your integration.
Copy link to headingFrequently Asked Questions
What is the difference between Voyage 4 Lite and voyage-4?
voyage-4is the mid-sized Voyage 4 model; Voyage AI by MongoDB reports it approaches voyage-3-large quality. Voyage 4 Lite uses fewer parameters; Voyage AI by MongoDB reports it approaches voyage-3.5 accuracy. Both share the same embedding space asvoyage-4-large.How does Voyage 4 Lite compare to voyage-3.5-lite?
Voyage 4 Lite is a Voyage 4 model with a shared embedding space and updated training. Voyage AI by MongoDB positions it near voyage-3.5 accuracy with fewer parameters. Moving from Voyage 3.x requires re-embedding.
What is the context window for Voyage 4 Lite?
32K tokens. Size chunks so single requests stay under this limit.
Is Voyage 4 Lite suitable for production use?
Yes. Voyage AI by MongoDB targets production for
voyage-4-lite, including asymmetric setups withvoyage-4-largedocument embeddings when query cost matters.How do I access Voyage 4 Lite through Vercel AI Gateway?
Add your Voyage AI by MongoDB API key in AI Gateway settings, then send embedding requests through AI Gateway. AI Gateway authenticates requests and records usage.
When should I move from Voyage 4 Lite to voyage-4 or voyage-4-large for queries?
Move when you need higher query-side accuracy. If documents stay on
voyage-4-large, you can upgrade query embeddings tovoyage-4orvoyage-4-largewithout re-vectorizing documents in that asymmetric setup.Do I need to re-embed my data to switch from voyage-3.5-lite?
Yes. Voyage 3 and Voyage 4 use different embedding spaces, so you re-embed when you change generations.
Your use is subject to Voyage AI by MongoDB's Terms & Privacy Policies.