Summarize this article with:
OpenRouter's new EU endpoint keeps requests in Europe, but only on its Business plan (8% fee) or Enterprise. Here is how it compares with Eden AI's EU endpoint on price, European providers and jurisdiction.
OpenRouter now offers EU in-region routing: send your requests to eu.openrouter.ai instead of openrouter.ai, and they are decrypted, processed and served inside the European Union. For European teams, that is good news. Data residency has long been the first question a DPO asks about any LLM gateway, and more options are better than fewer.
But "there is an EU endpoint" is only the start of the evaluation. Which plan do you need to use it? What does it cost on top of inference? Which providers actually serve your requests in Europe? And who is the company sitting in the middle of your traffic?
This article walks through how OpenRouter's EU endpoint works, where it fits, and why Eden AI's EU endpoint is often the simpler and cheaper choice for European teams. Plans and prices were checked on 17 October 2026.
How OpenRouter's EU endpoint works
OpenRouter shipped EU routing in late 2025 and added a US equivalent in September 2026. The mechanics are straightforward: you change the base URL to https://eu.openrouter.ai/api/v1, keep the same API key and model IDs, and only providers running inside the EU can serve the request. If no in-region provider offers the model, the request fails with a 404 instead of quietly leaving the region.
OpenRouter also makes a fair point about what a residency claim should mean: it is not enough for inference to run in Europe if the gateway itself decrypts your prompt somewhere else first. Its EU endpoint keeps the full request path in-region, and server tools that would send data outside the EU are disabled rather than falling back to global infrastructure. That is the right standard, and any gateway, Eden AI included, should be judged against it.
The catch is access. According to OpenRouter's own announcement, in-region routing is available on the Business and Enterprise plans only. It is not part of the standard pay-as-you-go plan.
The cost: an 8% fee to keep your data in Europe
OpenRouter does not mark up provider token prices. It makes money through a platform fee on credit purchases, and that fee depends on your plan:
| Plan | Platform fee | EU in-region routing |
|---|---|---|
| OpenRouter Standard (pay-as-you-go) | 5.5% | No |
| OpenRouter Business (pay-as-you-go) | 8% | Yes |
| OpenRouter Enterprise | Custom, by contract | Yes |
| Eden AI Self-serve (pay-as-you-go) | 5.5% | Yes, same API key |
In other words, a team that needs EU data residency on OpenRouter without signing an enterprise contract moves from a 5.5% fee to an 8% fee. On Eden AI, the EU endpoint is available with the same API key as the global endpoint, on the standard 5.5% self-serve fee.
To make that concrete: on $10,000 of monthly inference, the platform fee is roughly $800 at 8% and $550 at 5.5%. That is about $250 a month, or $3,000 a year, for the same EU-routed traffic. The gap grows linearly with volume.
Two honest caveats. First, enterprise pricing is negotiated on both sides, so large customers should compare actual quotes rather than list rates. Second, the fee is not the whole bill: token prices depend on which provider serves each model in the EU, so check the per-model price for the routes you actually use on either catalogue.
Plenty of European providers, not just EU regions of US clouds
OpenRouter's EU endpoint serves the subset of its catalogue that at least one provider can run inside the EU, for example GLM 5.2 served from Mistral's EU data centres. It is a solid list, but in-region routing tells you where a request runs, not who runs it.
Eden AI has made European providers a core part of its catalogue. The Eden AI model catalogue lists 100+ models hosted in the EU, served by companies that are themselves European: Mistral AI, OVHcloud and Scaleway in France, Nebius and GreenPT in the Netherlands, IONOS in Germany, Multiverse Computing in Spain, Infomaniak in Switzerland, TensorX and more. That gives you European infrastructure and a European operator at every hop, not only a European data centre.
It also means real choice. Where an open-weight model is served by several European providers, you can compare price, speed and context length between them and switch with a single parameter. The catalogue's EU hosting filter shows every model with at least one endpoint in Europe, alongside live speed and uptime measured on real traffic.
As on OpenRouter, a model that cannot run in Europe is simply not exposed on the EU endpoint, and there is no silent fallback to global infrastructure. You can check what is available before writing a line of code: the discovery endpoints at https://api.eu.edenai.run/v3/models and /v3/info are public and already filtered to EU-eligible providers and models.
Data residency is not the same as data sovereignty
Where your data is processed is one question. Who processes it, and which laws that company answers to, is another.
OpenRouter, Inc. is a US company. Its EU endpoint keeps your requests in Europe, but the gateway operator remains subject to US law. Whether that matters for your workload is a question for your legal and compliance team, not for a blog post. Many organisations are comfortable with EU residency from a US provider; others, especially in the public sector, healthcare and finance, prefer to keep the whole chain under European jurisdiction. We cover the distinction in more detail in EU data residency vs data sovereignty.
Eden AI is a French company, headquartered in Lyon, with its core infrastructure hosted in France. On the EU endpoint, that means the gateway, the routing and the inference can all sit under European jurisdiction when you choose European providers. Eden AI also provides:
- A Data Processing Agreement as standard, for GDPR Article 28.
- Zero data retention: Eden AI does not store prompts, files or outputs, and never trains on customer data.
- SOC 2 and ISO 27001 certification for the infrastructure behind the API.
OpenRouter EU vs Eden AI EU at a glance
| OpenRouter EU | Eden AI EU | |
|---|---|---|
| Base URL | eu.openrouter.ai/api/v1 | api.eu.edenai.run/v3 |
| Plans with EU routing | Business and Enterprise | Self-serve and Advanced |
| Pay-as-you-go platform fee | 8% (Business) | 5.5% |
| Markup on provider prices | None | None |
| European providers | Subset of its catalogue served from EU data centres | 100+ EU-hosted models from Mistral AI, OVHcloud, Scaleway, Nebius, IONOS, TensorX and more |
| Request path | Decrypted and processed in the EU | Hosted, processed and routed in the EU |
| Model not available in the EU | Request fails (404) | Request blocked, no fallback outside the EU |
| Company jurisdiction | United States | France (EU) |
When OpenRouter EU still makes sense
OpenRouter is a solid product, and its EU endpoint is well designed. It can be the right fit if you already run on an OpenRouter Enterprise contract with negotiated fees, if the specific models you need are available in its EU list, or if you rely on OpenRouter-specific features you do not want to migrate away from.
If you are choosing an EU gateway today, without that history, the questions to ask are simple: what will the fee be on your volume, does it give you access to the European providers you want, and does the operator's jurisdiction match your compliance requirements?
Switching takes one line of code
Eden AI's API is OpenAI-compatible, so moving EU traffic is mostly a base URL change. Start by listing the models available in the EU, then call one:
import requests
from openai import OpenAI
# Public discovery endpoint, already filtered to EU-eligible models
eu_models = requests.get("https://api.eu.edenai.run/v3/models").json()["data"]
print([m["id"] for m in eu_models][:20])
client = OpenAI(
base_url="https://api.eu.edenai.run/v3", # the only change from the global endpoint
api_key="YOUR_EDENAI_API_KEY", # same key as on api.edenai.run
)
response = client.chat.completions.create(
model=eu_models[0]["id"], # pick any model from the EU list
messages=[{"role": "user", "content": "Summarise why EU data residency matters."}],
)
print(response.choices[0].message.content)If you request a model that is not available in Europe, the EU endpoint returns an explicit error instead of routing elsewhere, so a misconfiguration fails loudly during testing rather than silently in production.
To get started, create your Eden AI API key, browse the EU endpoint page, or see our broader Eden AI vs OpenRouter comparison.
Frequently asked questions
Does OpenRouter have an EU endpoint?
Yes. OpenRouter offers EU in-region routing at eu.openrouter.ai. Requests are decrypted and processed inside the EU and only served by EU-based providers. It is available on the Business and Enterprise plans, not on the standard pay-as-you-go plan.
How much does OpenRouter's EU endpoint cost?
OpenRouter does not mark up token prices, but EU routing requires the Business plan, which carries an 8% platform fee on credit purchases, or an Enterprise contract with custom pricing. The standard plan's fee is 5.5%, but it does not include EU routing.
Is Eden AI's EU endpoint available on the self-serve plan?
Yes. Your Eden AI API key works on both the global endpoint and the EU endpoint, and the self-serve plan applies the same 5.5% platform fee with no markup on provider prices.
Which models can I use on Eden AI's EU endpoint?
Only models that can run on European infrastructure, served by European providers such as Mistral AI, OVHcloud, Scaleway, Nebius, IONOS, Infomaniak, GreenPT, Multiverse Computing and TensorX. Browse them with the EU hosting filter in the Eden AI model catalogue, or query https://api.eu.edenai.run/v3/models, with no API key required.
Is EU data residency enough for GDPR compliance?
It helps, because it avoids international data transfers, but it is not the whole picture. You also need a Data Processing Agreement, clear retention rules and, for some organisations, a gateway operator under European jurisdiction. Your DPO should assess the full chain: gateway, provider and any tools involved in the request.
Can I use both the global and EU endpoints with Eden AI?
Yes. Many teams route sensitive workloads through the EU endpoint and use the global endpoint for tasks where a model is only available outside Europe. Caching is region-scoped, so the two endpoints never share cached responses.

.jpg)

.png)