OpenAI compatible API · Attested · Public status

EU LLM Gateway Base URL & Data Residency

Use the Europe West EU LLM gateway base URL with OpenAI-compatible APIs, EU-focused routes, data-residency controls, and no prompt logs.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

EU entry pointeu.trustedrouter.com for Europe-focused setup.

EU API regionhttps://api-europe-west4.quillrouter.com/v1

EU aliastrustedrouter/eu prefers EU and privacy-forward routes.

Same trust modelTLS terminates inside the attested gateway.

EU deployment checklist

three separate controls

Gateway region: set the base URL to https://api-europe-west4.quillrouter.com/v1.
Provider geography: use trustedrouter/eu, then enforce your approved providers with provider.only.
Privacy posture: set provider.min_privacy to zdr or confidential when policy requires it.

Review current route health on the live leaderboard and cite stable history from the monthly benchmark reports.

What the EU LLM gateway controls

Europe West

An EU LLM gateway controls where your application connects to TrustedRouter and where routing decisions happen. Use https://api-europe-west4.quillrouter.com/v1 so authentication, policy checks, provider selection, and response streaming begin in Europe West inside the attested gateway.

Gateway region, provider region, and privacy posture are separate controls. The regional hostname selects the gateway. trustedrouter/eu prefers EU-focused routes. provider.only enforces your approved provider list, while provider.min_privacy enforces ZDR or confidential-compute requirements.

Europe-first routing

Use the EU gateway and an EU-focused model alias.

For European teams, start with the regional API hostname and the trustedrouter/eu model. The router prefers Mistral first, then EU-regionable and privacy-forward provider routes.

This is not a blanket data-residency guarantee for every upstream provider. For strict residency, pin approved providers in provider.only and keep that allowlist in the contract.

Review providers

EU routePython

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["TRUSTEDROUTER_API_KEY"],
    base_url="https://api-europe-west4.quillrouter.com/v1",
)

response = client.chat.completions.create(
    model="trustedrouter/eu",
    messages=[{"role": "user", "content": "Reply PONG."}],
    max_tokens=8,
)

Gateway

Terminate prompt TLS in Europe.

The EU regional hostname targets the Europe West attested gateway. It keeps the router hop close to European users and avoids the global convenience endpoint.

Providers

Prefer the right upstreams.

trustedrouter/eu restricts routing to an EU-focused provider set, led by Mistral and followed by privacy-forward providers with tracked policy notes.

Compliance

Use filters for hard rules.

For legal, healthcare, financial, or procurement-gated work, use trustedrouter/zdr, trustedrouter/e2e, or an explicit provider allowlist.

Provider filter example

strict mode

{
  "model": "trustedrouter/eu",
  "provider": {
    "only": ["mistral", "google-vertex"],
    "allow_fallbacks": true
  },
  "messages": [{"role": "user", "content": "Summarize this contract."}]
}

The alias narrows to the EU-focused pool first. A caller-supplied provider.only narrows it further.

EU AI infrastructure resources

All resources

EU AI models and providersWhich labs and which operators are registered in the EU
LLM data residencySeparate gateway, provider, and storage regions
GDPR-compliant LLM APIDPA, subprocessors, and routing evidence
EU AI ActEvidence for deployers and procurement teams
Private LLM APIAttestation, ZDR, and confidential provider routes
Provider directoryPrivacy posture and policy sources by provider
Monthly benchmark reportsStable first-party provider and route measurements

Questions

What is an EU LLM gateway?

An EU LLM gateway accepts your API connection in a European region, authenticates and routes the request there, and forwards it only to eligible model providers. TrustedRouter's Europe West gateway terminates TLS inside the same attested open-source workload as its other regional gateways.

Which URL should European applications use?

Use https://api-europe-west4.quillrouter.com/v1 as the OpenAI-compatible base URL. The trustedrouter/eu model alias prefers EU and privacy-forward routes. The eu.trustedrouter.com hostname is the Europe-focused product and setup page.

Does the EU gateway guarantee EU data residency?

The regional gateway keeps the TrustedRouter routing hop in Europe, but an upstream provider can process outside the EU. For a hard residency policy, combine the EU gateway with provider.only and a contractually approved provider allowlist. The router fails closed when no allowed route is available.

Can I require zero data retention on the EU gateway?

Yes. Use trustedrouter/zdr or set provider.min_privacy to zdr. This is separate from geography: the EU hostname controls the gateway region, while the privacy filter controls which downstream provider routes are eligible.