In-Region Routing: Keep your data in the US or EU
OpenRouter's Business and Enterprise plans can now pin requests to US-only providers via us.openrouter.ai, matching its existing EU routing.
OpenRouter has launched US In-Region Routing, joining the EU routing it shipped last October. Requests sent to us.openrouter.ai are decrypted inside the United States and routed only to providers running there, for the full lifecycle of the request; eu.openrouter.ai does the same for the EU. If no in-region provider serves a requested model, the request fails with a 404 rather than being routed elsewhere.
The regional endpoints cover models from OpenAI, Anthropic, Google, NVIDIA, Thinking Machines, DeepSeek, Moonshot, and Qwen, among others, served from in-region data centers such as Baseten, Fireworks, Azure, and Mistral. API keys, request bodies, and model IDs stay the same, and provider preferences, fallbacks, and privacy settings carry over from the account, so a single service can point at us.openrouter.ai while other traffic keeps using the global endpoint. In-Region Routing can also be enforced for a specific workspace, team, or API key through Guardrails.
In-Region Routing is available on Business and Enterprise plans. Full details are in the original announcement.
