Quick Start
Change Log
Settings and Permissions
Billing and Licensing
Assign Licenses for Agentforce Vibes
Usage Metrics
Estimate Flex Credits Usage
Enable Geo Aware Routing
Inline Auto Completion
Troubleshooting
FAQ
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 lists available models by region.
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.
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.
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 enable Turn Off Model Provider Region Fallback. 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.
This setting currently has no effect for Anthropic and Gemini models. Support for these models is coming soon.
Note
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:
1{
2 "settings": {
3 "agentforceForDevelopersSettings": {
4 "agentforceForDevelopersGeoAwareOptIn": true
5 }
6 }
7}