Regional inference is now generally available. Customers can send requests to a European endpoint (api.eu.mistral.ai) or a US endpoint (api.us.mistral.ai), and processing stays in that region. That matters for banks, government agencies, and insurers that need to prove customer data never leaves the EU. Shorter network paths also mean lower latency. Anyone using the default endpoint gets no guarantee about where their request is processed. Regional routing costs 10 percent on top of standard pricing.
EU data processing comes with significant limits
However, among the platform's add-on tools, only function calling works with regional endpoints, meaning the model's ability to trigger external APIs. Agents, batch processing, and file management aren't available at the regional addresses. Model selection varies by region, too. Mistral doesn't publish a fixed list, customers have to query each endpoint to see what's there.
The likely reason is the gap between a simple model query and storing intermediate state. A standard model call needs no persistent storage. Agents, batch jobs, and file storage hold data beyond a single call, things like intermediate steps or uploaded documents. Mistral calls these features "stateful." They probably require extra on-site infrastructure, though the company hasn't confirmed that.
