# Mistral AI just gave us a way to pin inference to the US or EU > Source: > Published: 2026-08-11 23:46:34+00:00 # Mistral AI just gave us a way to pin inference to the US or EU For those of us handling the actual deployment, it's a dead-simple config change. You just swap your base URL. If you need Europe, use `api.eu.mistral.ai` ; for the States, it's `api.us.mistral.ai` . If you stick with the default, you're on the global endpoint. ## The trade-offs and "gotchas" It isn't a magic button for total data sovereignty. I noticed a few things in the docs that might trip people up if they're just skimming. First, this only covers the *inference* (the actual prompt and completion). The "control plane"—think billing, account settings, and analytics—still isn't regionalized. So, while your customer's prompt stays in the EU, your billing info might not. Also, don't confuse this with "zero data retention." That's a separate policy you have to enable; picking a regional endpoint doesn't automatically mean Mistral isn't logging your data. Second, there's a "regional tax." Using these endpoints costs 1.1x more for inputs, outputs, and caching. For a small side project, it's nothing, but for a high-volume AI workflow, that 10% bump adds up. ## Technical limitations for LLM agents This is where it gets annoying for devs. If you're building a complex LLM agent, you need to check your feature list. Regional endpoints are way more limited than the global one. **Supported:** Function calling is currently the only regional tool that works.**Not Supported:** Agents, Batch processing, and the Files API are all missing. If your app relies on uploading massive PDFs via the Files API or needs asynchronous batching to save costs, you can't use regional endpoints yet. You're basically trading those "stateful" features for geographic control. ## Quick migration checklist If you're planning a move to a regional endpoint to satisfy a compliance officer, run through this before you push to prod: 1. Check if the specific model version you're using is actually hosted in that region. 2. Audit your code for any `Files API` or `Batch` calls—these will break. 3. Update your environment variables for the new base URL: ``` # Example for EU deployment MISTRAL_API_BASE="https://api.eu.mistral.ai" ``` 4. Factor that 10% price increase into your token budget. It's a solid step forward for enterprise deployments, but the lack of Files API support is a bit of a bottleneck for real-world [RAG](/en/tags/rag/) pipelines. [Next Can you actually build a detailed corporate pantry scene using →](/en/threads/5923/) ## All Replies （0） No replies yet — be the first!