Every Voyage AI model has a support status that indicates whether you can use the model for new projects and whether the model remains available through the Embedding and Reranking API. This page lists the current status of each model and records changes to those statuses over time.
For model specifications, such as context length and embedding dimensions, see Models Overview.
Scope
This support policy applies to Voyage AI embedding and reranking models served through the Atlas Embedding and Reranking API at ai.mongodb.com, including the models that Atlas Automated Embedding and Atlas Native Reranking use.
This support policy does not apply to models served through the legacy Voyage AI platform at api.voyageai.com, self-managed deployments, or third-party marketplace offerings.
MongoDB announces all lifecycle transitions on this page.
Supported Endpoints
The Atlas Embedding and Reranking API serves models through the following endpoints:
Endpoint | Description |
|---|---|
| The global endpoint. Serves every model listed on this page. |
| A geography-scoped endpoint that routes requests to infrastructure in the European Union. |
| A geography-scoped endpoint that routes requests to infrastructure in the United States. |
MongoDB adds geography-scoped endpoints over time. The Supported Endpoints column of the Current Model Status tables lists All for models that every endpoint serves, and ai.mongodb.com for models that only the global endpoint serves.
Model Statuses
Voyage AI models use the following support statuses:
Status | Description |
|---|---|
Preview | The model is fully supported but isn't yet the current model in its capability family. While a model is in Preview, its response behavior might change slightly as MongoDB fine-tunes the model weights. A Preview model doesn't supersede the current Active model in its family. The Active model becomes Legacy only when its successor becomes Active. |
Active | The model is the current model in its capability family and is recommended for new projects. MongoDB supports Active models with serving-infrastructure security patches, incremental improvements, and bug fixes. For the endpoints that serve each Active model, see the Supported Endpoints column of the Current Model Status table. |
Legacy | A newer model supersedes the model. MongoDB supports Legacy models with serving-infrastructure security patches and bug fixes. Legacy models remain available to all customers in existing supported geographies, but might not be available in newly launched geographies. To replace a Legacy model for a new project, use the model listed in the Recommended Replacement column of the Current Model Status table. |
Deprecated | The model remains callable but might be less reliable than Active models, and is no longer recommended. MongoDB continues to serve Deprecated models, but doesn't provide security patches, bug fixes, or incremental improvements for them. Each Deprecated model has a published retirement date and a named replacement. Organizations that already use a Deprecated model retain access to it until the retirement date. New organizations can't access Deprecated models and are directed to the current Active model instead. Migrate to the replacement before the retirement date. |
Retired | The model is no longer served. MongoDB doesn't support Retired models. Requests that specify a Retired model return an HTTP |
Support Duration and Notice
When MongoDB retires a model, MongoDB provides a named replacement model, a migration guide, and embedding model migration credits. Before each transition, MongoDB provides at least the following notice:
Transition | Embedding models | Reranker models |
|---|---|---|
Legacy to Deprecated | 12 months | 6 months |
Deprecated to Retired | 6 months | 3 months |
Legacy to Retired, total | 18 months | 9 months |
No Voyage AI model is currently Deprecated or Retired, and no model has a published retirement date. MongoDB does not provide support for models past their retirement date, or for models outside of the Atlas Embedding and Reranking API.
Current Model Status
Select a model family to view the status of each model in that family:
The Active Date is the date the model becomes the current model in its family. The Legacy Date is the date a newer model supersedes it. A Legacy Date in the future is a planned date and is subject to change. The Recommended Replacement is the model to use in place of a Legacy model for new projects. Supported Endpoints is the set of endpoints that serve the model, beginning 1 September 2026. To learn about each endpoint, see Supported Endpoints.
Changelog
This changelog records changes to model status. For the current status of all models, see Current Model Status.
1 September 2026
Added the Preview status.
rerank-3andrerank-3-liteare released in Preview.The following models are now Legacy, effective on the date listed. Each model remains available through the Embedding and Reranking API. For new projects, use the recommended replacement:
rerank-2, 11 August 2025, replaced byrerank-2.5rerank-2-lite, 11 August 2025, replaced byrerank-2.5-litevoyage-3.5, 15 January 2026, replaced byvoyage-4voyage-3.5-lite, 15 January 2026, replaced byvoyage-4-litevoyage-code-2, 15 January 2026, replaced byvoyage-code-4voyage-finance-2, 15 January 2026, replaced byvoyage-4voyage-law-2, 15 January 2026, replaced byvoyage-4-litevoyage-multimodal-3, 15 January 2026, replaced byvoyage-multimodal-3.5voyage-context-3, 30 June 2026, replaced byvoyage-context-4voyage-code-3, 13 August 2026, replaced byvoyage-code-4
Added the Active Date and Legacy Date for each model, the scope of the support policy, expanded status definitions, and the minimum notice windows for each lifecycle transition.
Added the list of Supported Endpoints and a Supported Endpoints column to the Current Model Status tables.
voyage-4,voyage-4-lite,voyage-4-large,voyage-code-4,voyage-context-4,voyage-multimodal-3.5,rerank-3, andrerank-3-liteare available through all endpoints. All other models are available only throughai.mongodb.com.
30 July 2026
- Baseline: all Voyage AI models are Active. Initial publication of model status tracking.