Protocols and compatibility
Each API configuration exposes only the unified routes implied by its published LiteLLM modes. Requests go directly to the Lumoswitch inference service and authenticate with the same Lumoswitch access key.
| Workflow | Methods | Public routes |
|---|---|---|
| Models and text | GET, POST | /v1/models, /v1/chat/completions, /v1/completions, /v1/embeddings |
| Responses | POST, GET, DELETE, WebSocket | /v1/responses, /v1/responses/{id}, /v1/responses/{id}/input_items, /v1/responses/compact, /v1/responses/{id}/cancel |
| Images and audio | POST | /v1/images/generations, /v1/images/edits, /v1/audio/transcriptions, /v1/audio/speech |
| Video | POST, GET | /v1/videos (create), /v1/videos/{id}, /v1/videos/{id}/content, /v1/videos/{id}/remix, /v1/videos/characters, /v1/videos/characters/{id}, /v1/videos/edits, /v1/videos/extensions |
| Document and ranking | POST | /v1/ocr, /v1/rerank, /v2/rerank, /v1/moderations |
| Realtime | POST, WebSocket | /v1/realtime, /v1/realtime/client_secrets, /v1/realtime/transcription_sessions, /v1/realtime/calls |
| Anthropic | POST | /v1/messages, /v1/messages/count_tokens |
| Gemini | POST | /v1beta/models/{model}:generateContent, :streamGenerateContent, :countTokens, plus /models aliases |
Batch/Files are private because the tenant-scoped Managed Files ownership hook in LiteLLM 1.102.0-rc.1 remains Enterprise-only; this project does not integrate that hook and cannot guarantee tenant isolation of shared upstream file resources. The global Video list is private for the same isolation reason. Image Variations, Assistants/Threads, Vector Stores/RAG, Containers, management APIs, and provider-native pass-through are also not public.
Use https://api.lumoswitch.com/v1 for OpenAI clients and https://api.lumoswitch.com for Anthropic or Gemini clients. Every failover candidate must support the capabilities used by the client.
Use the Lumoswitch access key in the client's native authentication header: Authorization: Bearer for OpenAI, x-api-key for Anthropic, or x-goog-api-key for Gemini. Never put an upstream provider key in a downstream client.
These are Lumoswitch Runtime's unified translation routes: an Anthropic- or Gemini-shaped client can target any compatible configured upstream. Native provider pass-through paths such as /anthropic/*, /gemini/*, and /cohere/* remain private because they do not use the configuration's model and credential boundary. Nginx enforces the exact method, MIME type, body-size limit, and WebSocket upgrade contract before LiteLLM applies Virtual Key model authorization, rate limits, concurrency, and budget controls.