Dokumentation

Hur du anropar API:et, vad routern gör med en policy, vilka klasser för datahemvist som finns, vad en spårning registrerar — och varje felkod, slutpunkt och gräns, genererad från koden som upprätthåller dem.

Kom igång

Snabbstart

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.

Konsol

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.

Migrering

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.

API-referens

The LLM EU API reference: chat completions, models, embeddings, the platform API, and every error code with the HTTP status that carries it.

Referens

Autentisering

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.

Slutpunkter

Every route this API mounts with the credential it needs, plus the OpenAI endpoints that are deliberately absent and what they answer instead.

Fel

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.

Hastighetsbegränsningar

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.

Strömning

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.

Policyer

The policy object field by field: residency classes, allow and deny lists, daily budget, retention, data classes and partner endpoints, with their defaults.

Dirigering och policy

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.

Datahemvist och regioner

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.

Bevis och verifiering

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.

OpenAI-kompatibilitet

The exact OpenAI compatibility contract: accepted request fields, the response shape, SSE streaming frames, and what is intentionally not supported.

Drift

Egen hosting

Running the stack yourself: Node 22, zero dependencies, SQLite, the operator CLI, the environment, backups and the mail transport.