Démarrage rapide
Point any OpenAI-compatible client at the LLM EU base URL and call llmeu-auto. Copy-paste snippets for cURL, Python and JavaScript, with the llmeu response block explained.
Documentation
Comment appeler l’API, ce que le routeur fait d’une politique, quelles classes de résidence existent, ce qu’une trace enregistre — et chaque code d’erreur, point de terminaison et limite, généré à partir du code qui les applique.
Pour commencer
Console
What each page of the signed-in console does, the five roles and what they may change, and what a person can change about their own account.
Migration
Moving an existing OpenAI integration onto LLM EU: the base URL change, the fields that carry over, the endpoints that do not exist, and how to take your data out again.
Référence API
The LLM EU API reference: chat completions, models, embeddings, the platform API, and every error code with the HTTP status that carries it.
Référence
Authentification
API keys, the three scopes, why a signed-in browser cannot call the API, and how revocation works. Rendered from the scopes the API enforces.
Points de terminaison
Every route this API mounts with the credential it needs, plus the OpenAI endpoints that are deliberately absent and what they answer instead.
Erreurs
Every error code the API can answer with, the HTTP status and type that carry it, and what to do about each. Checked against the source by a test.
Limites de débit
The limits this deployment applies per key, per organization and per IP address, rendered from the table the limiter reads, and what a 429 actually contains.
Streaming
The SSE wire format for streamed completions, the frames, the routing block on the last frame, and what happens to the trace when a client disconnects.
Politiques
The policy object field by field: residency classes, allow and deny lists, daily budget, retention, data classes and partner endpoints, with their defaults.
Routage et politique
How the LLM EU router chooses an endpoint: the filter order, the scoring weights, why residency is a filter and never a preference, and how failover stays inside the policy.
Résidence et régions
The four residency classes defined in plain language, which regions exist, and how a policy constrains where a request may be processed. No silent fallback.
Preuves et vérification
What is recorded for every call, what is deliberately not, and how to export an audit bundle a data protection officer can read without asking you.
Compatibilité OpenAI
The exact OpenAI compatibility contract: accepted request fields, the response shape, SSE streaming frames, and what is intentionally not supported.
Exploitation
Auto-hébergement
Running the stack yourself: Node 22, zero dependencies, SQLite, the operator CLI, the environment, backups and the mail transport.