Geographies for Voyage AI Inference

For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

Geographies for Voyage AI Inference

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
ai.mongodb.com Unscoped. Atlas can serve the request from any Geography.
eu.ai.mongodb.com Europe
us.ai.mongodb.com 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.](https://www.mongodb.com/docs/voyageai/api-reference/overview.md#std-label-voyage-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.](https://www.mongodb.com/docs/voyageai/models/lifecycle.md#std-label-voyage-model-lifecycle

To learn more about each model, see [Voyage AI Embedding and Reranking Models Overview.](https://www.mongodb.com/docs/voyageai/models.md#std-label-voyage-models

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.](https://www.mongodb.com/docs/voyageai/management/api-keys.md#std-label-voyage-api-key-scope

  • To require that new model API keys use a given Geography, see [Restrict Model API Key Scope Using a Resource Policy.](https://www.mongodb.com/docs/voyageai/management/api-keys.md#std-label-voyage-api-key-scope-resource-policy

  • To send requests to a Geography's endpoint from the REST API or a client library, see [Scoped Endpoints.](https://www.mongodb.com/docs/voyageai/api-and-clients.md#std-label-voyage-scoped-endpoints

  • To learn how keys and endpoints correspond, see [Endpoints.](https://www.mongodb.com/docs/voyageai/api-reference/overview.md#std-label-voyage-api-endpoints

  • To review the rate limits that apply to scoped endpoints, see [Geography Rate Limits.](https://www.mongodb.com/docs/voyageai/management/rate-limits.md#std-label-voyage-geography-rate-limits

  • To filter and segment your usage data by Geography, see [Usage by Geography.](https://www.mongodb.com/docs/voyageai/management/monitor-usage.md#std-label-voyage-usage-by-geography