EU in-region routing for your LLM API calls

OpenRouter Business routes requests sent to eu.openrouter.ai only to shared provider endpoints in Europe (the EU/EEA, the UK, and Switzerland), so prompts and completions are processed there, for EU data residency. Requests served by your own BYOK key go to your deployment's region, which you control.

8% platform fee on credit purchases, no monthly minimum, no contract.

Models available through eu.openrouter.ai

Read from the EU Models API and refreshed hourly. Prices are the EU endpoints' input and output token prices in US dollars per million tokens; other charges, such as images, caching, or web search, are on each model page.

models
69
providers
5
EU providers
Favicon for amazon
Amazon: Nova 2 Lite
  • Amazon Bedrock
  • $0.30
  • $2.50
Favicon for amazon
Amazon: Nova Lite 1.0
  • Amazon Bedrock
  • $0.06
  • $0.24
Favicon for amazon
Amazon: Nova Micro 1.0
  • Amazon Bedrock
  • $0.035
  • $0.14
Favicon for amazon
Amazon: Nova Pro 1.0
  • Amazon Bedrock
  • $0.80
  • $3.20
Favicon for anthropic
Anthropic: Claude Fable 5
  • Google
  • $11.00
  • $55.00
Favicon for anthropic
Anthropic: Claude Haiku 4.5
  • Amazon Bedrock
  • Google
  • $1.10
  • $1.10
  • $5.50
  • $5.50
Favicon for anthropic
Anthropic: Claude Haiku 5.5
  • Amazon Bedrock
  • Google
  • $0.11
  • $0.11
  • $0.55
  • $0.55
Favicon for anthropic
Anthropic: Claude Opus 4.5
  • Amazon Bedrock
  • $5.50
  • $27.50

What is processed where

In-region routing covers API payloads sent to eu.openrouter.ai. It does not move account or operational records, and it cannot change where resources you control are hosted.

Processed in Europe (requests to eu.openrouter.ai)

  • Prompts and completions, decrypted in the EU and routed only to shared provider endpoints located in Europe (the EU/EEA, the UK, and Switzerland). Requests served by your BYOK key go to your own deployment instead.
  • Endpoint selection: only shared endpoints onboarded for the EU region are candidates, so a request with no eligible endpoint fails instead of leaving the region.
  • Server tools that run entirely in-region, such as tool search, datetime, and apply patch, and native PDF parsing.
  • Broadcast traces for EU requests, sent from infrastructure inside the region and never queued outside it.

Account and billing metadata

This card covers account, billing and security records. Prompts and completions sent to eu.openrouter.ai are processed in Europe, except requests served by your own BYOK key, which go to your deployment.

  • Account data, billing records, and authentication data.
  • Security logs, abuse-monitoring metadata, and other operational records.

What you configure

  • Sending EU workloads to eu.openrouter.ai, and enforcing it with a data-region guardrail.
  • BYOK: where your own Bedrock, Azure, or Vertex deployment runs, and each key's region settings, which differ by provider. Regional routing and guardrails do not verify or move resources in your account.
  • Broadcast destinations: host your collector, Langfuse instance, or bucket in the EU if observability data must stay in the region.

EU providers

  • Favicon for Azure
    Azure24 modelsEurope
  • Favicon for Mistral
    Mistral20 modelsEurope
  • Favicon for Amazon Bedrock
    Amazon Bedrock16 modelsEurope
  • Favicon for Google
    Google13 modelsEurope
  • Inceptron6 modelsEurope

Source: the in-region routing docs.

How it works

How EU in-region routing works

Endpoint you call

eu.openrouter.ai

Routed only inside Europe

Shared provider endpoints in the EU/EEA, the UK and Switzerland.

No endpoint in Europe

The request fails rather than leaving the region.

  • Same key, same account

    There is no separate EU account or EU key. The API key you use on openrouter.ai works on eu.openrouter.ai once your organization is on Business.

  • Change the base URL

    Point your client at https://eu.openrouter.ai/api/v1. The request is decrypted in the EU and only shared provider endpoints in Europe (the EU/EEA, the UK, and Switzerland) are eligible to serve it.

  • Fails closed

    If no eligible endpoint is available for the model, the request errors instead of leaving the region. OpenRouter never silently falls back to a shared endpoint outside the region. Requests served by your BYOK key go to the deployment it is configured for, so keep it in the region you need.

  • Out-of-region features are rejected

    Features whose infrastructure processes data outside the region return an error on eu.openrouter.ai: web search, web fetch, files, image generation, Fusion, shell, sandboxed bash, PDF engines other than native, the Batch API (its jobs run on US-based storage and queueing infrastructure and are only accepted on openrouter.ai), and multi-model routers such as the Auto Router.

curl https://eu.openrouter.ai/api/v1/chat/completions \
  -H "Authorization: Bearer <OPENROUTER_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "anthropic/claude-sonnet-5",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

The full, current list of what regional domains reject is in Feature availability.

Enforce it

Enforce EU routing with a data-region guardrail

The base URL is a per-request choice. A guardrail makes it a rule, at the workspace, member, or API-key level.

  1. 1

    Workspace

    Set Data regions to EU on the workspace default guardrail. Every request in the workspace must then arrive through eu.openrouter.ai.

  2. 2

    Member

    Assign a guardrail with Data regions set to EU to an organization member. It applies to all of their API keys and chatroom usage.

  3. 3

    API key

    Assign a guardrail directly to a key. Guardrails intersect, so a key or member guardrail can only narrow the regions the workspace allows.

Shell
curl -X PATCH https://openrouter.ai/api/v1/guardrails/GUARDRAIL_ID \
  -H "Authorization: Bearer <OPENROUTER_MANAGEMENT_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "allowed_data_regions": ["europe"]
  }'

A request that arrives through a domain the guardrail does not allow is rejected with 403 Forbidden before any inference or endpoint selection. Data-region guardrails require a Business or Enterprise plan. The guardrail value for the EU is europe; the Models API filter is region=eu.

Setup in the editor and the API: Enforcing in-region routing with guardrails.

Guardrails docs

FAQ

OpenRouter EU questions

Already on OpenRouter?

Same account, same API key: upgrade to Business and change the base URL.

  • An organization admin upgrades in Settings > Manage plan
  • Your API keys and integration keep working
  • Send requests to https://eu.openrouter.ai/api/v1
  • Enforce it with a data-region guardrail

New to OpenRouter?

Create an account, then move your organization to Business.

  • No contract and no monthly minimum
  • 8% platform fee on credit purchases
  • A GDPR DPA with Standard Contractual Clauses
  • The EU catalog on this page, refreshed hourly
Ask about OpenRouter EU on
  • Favicon for openai
  • Favicon for anthropic
  • Favicon for perplexity
  • Favicon for x-ai