Quick answer
Mistral Regional Endpoints currently exclude Agents, Batch, and the Files API. Function calling is the only supported regional tool, and model availability varies by region.
If a workload depends on an unsupported feature, its regional-processing guarantee does not apply merely because another request in the workflow uses an EU or US base URL. Use the regional readiness checker to classify the whole path.
Current feature boundary
| Workload element | Regional status in current docs | Design response |
|---|---|---|
| Chat or completion inference | Supported for available regional models | Call the exact EU or US endpoint |
| Function calling | Supported regional tool | Keep tools and downstream data paths independently scoped |
| Agents | Not available | Rebuild orchestration outside the unsupported provider surface or use global |
| Batch | Not available | Use global Batch or redesign as eligible regional requests |
| Files API | Not available | Keep file storage and retrieval outside the claimed regional path |
| Other provider tools | Not currently supported | Do not silently fall through to global tools |
The model ID stays the same across global and regional APIs, but the target region must host that model. Query available models against the regional base URL before production traffic.
Avoid silent global fallback
Do not catch a regional feature error and automatically retry the request against api.mistral.ai unless policy explicitly permits global processing and records that decision. A successful retry may violate the workload’s data-location requirement.
Gate the route before sending data: region, model, feature, tool, retention, and downstream storage must all pass. Log the endpoint hostname, model ID, request identifier, timestamp, and policy result for every request.
Orchestration alternatives
For a workflow that needs agent state, batch jobs, or file retrieval, choose deliberately among:
- global Mistral features with an approved global data path;
- application-managed state and storage with eligible regional inference calls;
- a different regional service that supports the required surface;
- postponing the workload until Mistral documents support.
None of these choices automatically regionalizes the control plane. Read the EU/US data-location guide and compare the global endpoint tradeoffs.
Frequently asked questions
Do Mistral Regional Endpoints support Agents?
Not in the reviewed documentation. Mistral lists Agents, Batch, and the Files API as unavailable on regional endpoints.
Which tools work on regional endpoints?
Mistral currently documents function calling as the only supported regional tool. Verify the exact model and endpoint before traffic is moved.
Can a proxy make an unsupported regional feature compliant?
No. A proxy can preserve routing evidence, but it cannot make unsupported provider features regional. The actual Mistral base URL and eligible feature path determine processing geography.
Official sources
Source check: August 12, 2026. Recheck feature, tool, model, region, SDK, and endpoint support before routing production traffic.