Note
Public Preview
The Europe Geography and its endpoint, eu.ai.mongodb.com, are available as a Public Preview feature. The feature and the corresponding documentation might change at any time during the Preview period.
A Geography is a named group of cloud provider regions inside which Atlas processes the content that you submit for inference through the Embedding and Reranking API. A Geography is not the same as the cloud provider region where your Atlas cluster runs. The cluster region governs where Atlas stores your cluster's data, while the inference Geography governs where Atlas processes your content for inference, and you set each one separately.
When you scope a model API key to a Geography, requests that use that key run on Voyage AI models hosted inside that Geography. To learn more about the Geography concept, including the available Geographies and the Designated Services that honor them, see Geographies and Designated Services in Atlas.
Embedding and Reranking API Geography Endpoints
Each Geography has its own Embedding and Reranking API endpoint. The endpoint that you call must match the Geography that your model API key is scoped to.
Endpoint | Geography |
|---|---|
| Unscoped. Atlas can serve the request from any Geography. |
| Europe |
| United States |
Scoped endpoints follow the pattern <geography>.ai.mongodb.com, where <geography> is the geography value of the model API key that you send with the request.
To create a key that is not scoped to a Geography, set geography to any. To learn how keys and endpoints correspond, see Embedding and Reranking API Overview.
To learn what a Geography guarantees and how to decide whether to scope a key to one, see Geographies and Designated Services in Atlas.
Models Available in Geographies
Scoped endpoints don't serve every Voyage AI model. The Supported Endpoints column of the model tables lists All for models that every endpoint serves, and ai.mongodb.com for models that only the unscoped endpoint serves.
To check which endpoints serve a given model, see Model Deprecations, Lifecycle States, and Support.
To learn more about each model, see Models Overview.
Manage Geography Scoped Resources
To work with Geography scoped resources, see the following sections:
To create a model API key scoped to a Geography, see Key Scope.
To require that new model API keys use a given Geography, see Restrict Model API Key Scope Using a Resource Policy.
To send requests to a Geography's endpoint from the REST API or a client library, see Scoped Endpoints.
To learn how keys and endpoints correspond, see Endpoints.
To review the rate limits that apply to scoped endpoints, see Geography Rate Limits.
To filter and segment your usage data by Geography, see Usage by Geography.