OpenAI compatible API · Attested · Public status

EU AI Models & EU-Operated Providers

Models built by EU labs, providers operated from EU member states, and why an EU-registered provider is not by itself EU data residency.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

European labs, European operators, and the gap between them

An EU-registered provider is not the same thing as EU data residency. This page keeps the two apart.

Two facts get sold as one. The lab that trained a model has a country: 10 models in the catalog come from 1 lab registered in an EU member state. The company operating the endpoint a request reaches has its own country, and it is a different field: 3 of the 51 providers here are operated by a company registered in the EU.

Neither field is a residency guarantee. TrustedRouter records the operator's legal home, read from its own terms or filing. It does not record which datacentre answers a given request, so nothing on this page should be read as one. Where residency is contractual, it comes from an allowlist you pin and a contract you sign, not from a country code on a directory page.

Read the EU routing guide GDPR evidence

eu_route.pyPython

from openai import OpenAI

client = OpenAI(
    # EU gateway region, separate from provider choice
    base_url="https://api-europe-west4.quillrouter.com/v1",
    api_key="sk-tr-...",  # your TrustedRouter key
)

reply = client.chat.completions.create(
    model="trustedrouter/eu",
    messages=[{"role": "user",
               "content": "Summarize this contract."}],
    # strict mode: the exact operators you approved
    extra_body={"provider": {"only": ["mistral", "nebius"]}},
)

What trustedrouter/eu does, and what it does not do

routing preference

trustedrouter/eu is a model alias. Calling it routes over an EU-focused candidate pool led by Mistral, followed by providers with EU regions and privacy-forward posture. That pool is a preference expressed in the catalog, and its members are chosen for EU-focused availability rather than for being EU-registered companies. Most of that pool is operated from outside the EU, and the directory below names every operator country in the catalog so you can check rather than assume.

Gateway region is the base URL. https://api-europe-west4.quillrouter.com/v1 begins authentication, policy checks, provider selection, and streaming in Europe West, inside the attested gateway.
Provider selection is the model id and the request preferences. trustedrouter/eu prefers the EU-focused pool; provider.only narrows it to an exact allowlist and fails closed instead of falling back elsewhere.
Privacy posture is provider.min_privacy, set to zdr or confidential. It is orthogonal to jurisdiction: an EU-registered provider can record no privacy claim, and a non-EU one can be zero-retention.

The provider.jurisdiction preference accepts us and nothing else today. There is no eu value to set, so an EU jurisdiction requirement is expressed with provider.only and the providers listed below. Saying otherwise would give you a filter that does not exist. TrustedRouter never logs prompt or output content. Ordinary synchronous and streaming inference does not retain it. The opt-in Batch API temporarily retains enclave-encrypted artifacts for up to 30 days.

The full EU deployment checklist, including the regional hostname and the strict-mode request shape, is on the EU routing page. Compliance context for deployers is on EU AI Act evidence and data residency.

Live catalog, as of August 2026

Two separate facts: who operates the endpoint, and who built the model.

Counts below are read from the routes configured in TrustedRouter right now. Operator country is the legal home of the company running the endpoint a request reaches, taken from that company's own terms, privacy policy, or regulatory filing. It is not a claim about which datacentre serves the request.

3providers operated from the European Union

1lab with models here

10models from those labs

51providers in the catalog

467callable catalog models

2providers whose operator we could not establish

Providers operated from an EU member state

3 of 51

Send a request to one of these and the operator is a company headquartered in the European Union — head office, not place of registration. Privacy tier is a separate column: it is the highest bar we have recorded from that provider's published policy.

Provider	Operator country	Privacy tier	Recorded claims	Models served	Policy source
Nebius Token Factorynebius	Netherlands	Zero retention	ZDR	30	policy
Inceptroninceptron	Sweden	Zero retention	ZDR	5	policy
Mistralmistral	France	Standard	no verified privacy claim	5	policy

Every provider's full policy note and route list is on its own page. 2 providers in the catalog publish no operator TrustedRouter could pin down, so they appear in no jurisdiction list on this site and no request preference treats them as matching one. Review every provider.

Models built by EU labs

10 models

Grouped by the lab that built the weights, with the source TrustedRouter read that from. The operator columns show who runs the endpoints for each route, which is a different question from the lab's country and frequently a different answer.

Mistral AI 10 models

Mistral AI is a French SAS registered at 15 rue des Halles, 75001 Paris, RCS Paris 952 418 325. Source.

Model	Context	Routes	Operator jurisdictions	EU-operated routes
`mistralai/mistral-nemo` Mistral: Mistral Nemo	131,072	6	United States ×2 France ×1	Mistral
`mistralai/codestral-2508` Mistral: Codestral 2508	256,000	2	France ×1	Mistral
`mistralai/ministral-3-14b-instruct` Ministral 3 14B Instruct	262,144	2	United States ×1	none configured
`mistralai/mistral-large` Mistral Large	128,000	2	France ×1	Mistral
`mistralai/mistral-medium-3-5` Mistral: Mistral Medium 3.5	262,144	2	France ×1	Mistral
`mistralai/mistral-nemo-instruct-2407` mistralai/Mistral-Nemo-Instruct-2407	131,072	2	United States ×1	none configured

4 further Mistral AI models are in the catalog, ranked below these by route count. Browse every model.

Model origin is keyed by the vendor prefix of a model id, and a prefix earns a row once at least three of its models are in the catalog. 40 callable catalog models sit under a prefix below that line and carry no recorded origin, so they are on no page here rather than assigned a country by guesswork.

Browse every model Review provider policies AI models from the United States AI models from China

Choice

EU model or EU operator.

You can run an EU-built model on a US operator, or a US-built model on an EU operator. The two columns above let you pick each one deliberately instead of inheriting whichever the brand name suggests.

Contract

Paper, where paper is required.

A directory is evidence, not a commitment. The DPA, subprocessor list, and an agreed provider.only allowlist are what a European procurement review can hold someone to.

Proof

The gateway hop is checkable.

Whichever provider serves the request, the TrustedRouter hop can be attested live: a JWT signed by the CPU vendor's root key, bound to your TLS session. The procedure is on the security page.

Live catalog evidence

Current routes, prices, privacy, and measured performance.

Catalog facts come from the routes currently configured in TrustedRouter. Performance uses the same cached metadata snapshot as the public leaderboard. Prompts and outputs are not part of these measurements.

493public models

51providers

1513configured routes

299ZDR routes

32provider E2EE routes

2985recent availability samples

Model	Providers	Context	Input	Output	Privacy	Measured route
Mistral: Mistral Nemo`mistralai/mistral-nemo`	6 routes	131,072	$0.025848/1M to $0.0422/1M	$0.103179/1M to $0.17935/1M	E2EE	2193 ms TTFT mistral · 100.00% available · n=13
Mistral Large`mistralai/mistral-large`	2 routes	128,000	$0.5275/1M	$1.5825/1M	varies	2592 ms TTFT mistral · 24 tok/s · 100.00% available · n=11
Mistral: Mistral Medium 3.5`mistralai/mistral-medium-3-5`	2 routes	262,144	$1.5825/1M	$7.9125/1M	varies	2810 ms TTFT mistral · 100.00% available · n=10
Mistral: Codestral 2508`mistralai/codestral-2508`	2 routes	256,000	$0.3165/1M	$0.9495/1M	varies	2408 ms TTFT mistral · 100 tok/s · 100.00% available · n=5
Mistral: Mistral Small 4`mistralai/mistral-small-2603`	2 routes	262,144	$0.15825/1M	$0.633/1M	varies	1290 ms TTFT mistral · 100.00% available · n=5
Ministral 3 14B Instruct`mistralai/ministral-3-14b-instruct`	2 routes	262,144	$0.211/1M	$0.211/1M	varies	1265 ms TTFT digitalocean · 100.00% available · n=2

MistralPolicy varies 5 models 2408 ms p50 · n=44

Novita AIPolicy varies 111 models 2653 ms p50 · n=47

ChutesProvider E2EE 10 models 13134 ms p50 · n=39

DigitalOcean Gradient AIPolicy varies 18 models 1378 ms p50 · n=34

TinfoilProvider E2EE 6 models 3334 ms p50 · n=60

AnthropicPolicy varies 10 models 3176 ms p50 · n=59

OpenAIZDR on prepaid 44 models 1617 ms p50 · n=75

Google Vertex AIZDR on prepaid 10 models 2575 ms p50 · n=41

Browse every model Review provider policies Open the full leaderboardSnapshot 2026-08-20T18:23:14.976Z

Questions

Which AI models are made in the EU?

TrustedRouter groups catalog models by the lab that built them, using a country read from that lab's own legal notice or filing. The EU AI models page lists every lab registered in an EU member state alongside its models and the source the country came from. A vendor prefix earns an origin row once at least three of its models are in the catalog, so smaller prefixes appear on no region page rather than being assigned a country by guesswork.

Does the trustedrouter/eu route guarantee EU data residency?

No. trustedrouter/eu is a routing preference: it narrows candidates to an EU-focused provider pool led by Mistral. Membership in that pool is based on EU-focused availability and privacy posture, and some of its providers are operated by companies registered outside the EU. For a hard requirement, set provider.only to the operators you approved, which fails closed instead of falling back, and put that allowlist in the contract.

Can I require an EU provider the way I can require a US one?

Not with the jurisdiction preference. provider.jurisdiction accepts "us" and nothing else today, so an EU requirement is expressed with provider.only and the provider list on this page. Separately, the EU gateway region is chosen by base URL: https://api-europe-west4.quillrouter.com/v1 begins authentication, policy checks, provider selection, and streaming in Europe West inside the attested gateway.

Is provider jurisdiction the same as provider privacy posture?

No, they are independent fields. A provider registered in an EU member state can have no recorded zero-retention or confidential-compute claim, and a provider registered elsewhere can have both. Jurisdiction is filtered with provider.only; retention and confidentiality are filtered with provider.min_privacy set to zdr or confidential.