In-Region Routing: Route inference in the US or EU
By Steven Van ·
US and EU routing keeps prompts and completions in-region on Business and Enterprise plans, including DeepSeek, Kimi and GLM models.
Business and Enterprise customers can now keep OpenRouter requests inside the United States. OpenRouter has added US In-Region Routing alongside the EU routing it shipped last October. Requests sent to us.openrouter.ai are decrypted inside the US and routed only to shared provider endpoints there. eu.openrouter.ai does the same for Europe (the EU/EEA, the UK and Switzerland).
How it works
Developers swap the base URL for https://us.openrouter.ai/api/v1 or https://eu.openrouter.ai/api/v1. The API key, request body and model IDs stay the same, and provider preferences, fallbacks and privacy settings carry over from the account. One service can use the regional hostname while the rest of the traffic stays on openrouter.ai.
Requests served by a user's own BYOK key go to the deployment's region, which the user controls. If no eligible endpoint (shared, BYOK or private) can serve the model in that region, the request fails with a 404 (No endpoints found supporting your data region.) instead of being routed elsewhere.
Models available
The regional endpoints serve a subset of the global catalog under the same model IDs. A model is listed for a region if at least one provider can serve it from inside that region. The list can be checked by calling /api/v1/models through the regional domain, or by filtering the models page by In-Region Routing.
Models available for the US today include GPT-5.6, Claude Opus 5, Gemini 3.6 Flash, Grok 4.6, NVIDIA Nemotron 3 Ultra, Thinking Machines Inkling, DeepSeek V4 Pro, Kimi K3, GLM 5.2, gpt-oss-120b and Qwen3 Coder.
Chinese open-weight models are included. DeepSeek V4 Pro, Kimi K3 and GLM 5.2 are available for US routing because Baseten, Fireworks and Azure serve them from US data centers. GLM 5.2 is also available in the EU, served from Mistral's EU data centers. When a US or EU provider hosts a model, requests go to that provider and the lab is not involved.
Server tools and enforcement
OpenRouter says it evaluates server tools and the data jurisdictions they run in before offering them in a region. Tools that would send data outside the region are disabled rather than falling back to global infrastructure.
Teams can enforce a region for a workspace, team or API key with Guardrails. Setting the allowed data regions to one region makes OpenRouter reject any covered request that arrives on another hostname. This can be configured under Guardrails in settings or through the Management API.
Availability
In-Region Routing is available on the Business and Enterprise plans.
