---
schema_version: "1"
id: ff1c89f1aa737f13885c6dcb930348c84faa2dfe5803718a1e37dfa860b5bf44
title: Geo-Aware Model Routing for Agentforce Vibes
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/agentforcevibes/guides/files/afv-geo-aware-routing.md
canonical_url: https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-geo-aware-routing.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: dc12f7a0d66a52afcbd61a921f303916b411a307c1cfd3b412342be0759b5a6b
products:
  - Agentforce Vibes Developer Guide
  - salesforcedx
---
# Geo-Aware Model Routing for Agentforce Vibes

Agentforce Vibes supports geo-aware model routing. When your Salesforce admin enables geo-aware model routing, Agentforce Vibes routes all large language model (LLM) requests to the model endpoint geographically closest to your Salesforce org and the model picker shows only the models available in your org's region. This [document](https://help.salesforce.com/s/articleView?id=ai.generative_ai_large_language_model_support.htm&type=5) lists available models by region.

## Enable Geo-Aware Model Routing

To turn on **Geo-Aware Routing**, go to **Setup** in your org, search for **Agentforce Vibes Extension**, and turn on **Enable Geo-Aware Routing for this Org**.

## Turn off United States Fallback

Before you can turn off the final fallback to the United States, you must turn on Data 360. Data 360 is automatically provisioned when a Data Cloud license is added to your Salesforce org. See [Turn On Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_setup_provision.htm&type=5).

If you also want to prevent requests from falling back to the **United States** when the primary model endpoint is unavailable, go to **Einstein Setup** and toggle **Enable In-Region Model Request Only**. With this setting enabled, the system still attempts requests on the primary model endpoints first. If those endpoints are unavailable, the system returns an error instead of routing the request to the United States.

**note:** This setting currently has no effect for Anthropic and Gemini models. Support for these models is coming soon.

## Configure Geo-Aware Routing for Scratch Orgs

Scratch orgs don't inherit org settings. Explicitly set the geo-aware routing setting in your scratch org definition file.

Add the setting to `config/project-scratch-def.json`:

```json
{
  "settings": {
    "agentforceForDevelopersSettings": {
      "agentforceForDevelopersGeoAwareOptIn": true
    }
  }
}
```

## Considerations

- **Model picker reflects your region.** With geo-aware routing on, only region-served models appear in the model picker.
- **Feature availability.** The geo-aware routing feature is available in Summer '26, August monthly release.
- **Fallback behavior.** By default (fallback on), an unavailable regional endpoint routes a request to the United States. With fallback turned off, unavailable regional endpoints cause request failures.

## See Also

- [Geo-Aware LLM Request Routing](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing.htm&type=5)
- [Geo-Aware Routing for OpenAI Models](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing_openai.htm&type=5)
- [Large Language Model Support](https://help.salesforce.com/s/articleView?id=ai.generative_ai_large_language_model_support.htm&type=5)
- [Administer Agentforce Vibes](https://developer.salesforce.com/docs/platform/agentforcevibes/guide/afv-admin-settings.md)
