Authentication
LootVM authenticates API clients with a LootVM-issued API key. Upstream provider credentials stay on the gateway; your application only sends the LootVM key.
The same key works for OpenAI-compatible routes (for example Chat Completions) and Anthropic-compatible Messages (POST /v1/messages).
Create a key
Section titled “Create a key”- Sign in to the Console.
- Create an API key and assign the groups or model access your policy requires.
- Copy the secret when it is shown and store it in your secret manager or environment.
Treat the key like a password. Do not commit it to source control or put it in client-side browser code that you do not fully control.
Send the key
Section titled “Send the key”Bearer (all guides)
Section titled “Bearer (all guides)”Authorization: Bearer <lootvm-api-key>Example:
curl --fail-with-body https://api.lootvm.com/v1/models \ -H "Authorization: Bearer ${LOOTVM_KEY}"x-api-key (Messages and models)
Section titled “x-api-key (Messages and models)”On /v1/messages and /v1/models, Anthropic-style clients may send:
x-api-key: <lootvm-api-key>anthropic-version: 2023-06-01LootVM accepts x-api-key on those paths and treats it like the LootVM API key. Prefer also sending anthropic-version when you use the Messages API so Anthropic SDKs and clients behave as expected.
Do not mix a LootVM key with an upstream Anthropic console key on api.lootvm.com.
Base URL
Section titled “Base URL”All paths in these guides use:
https://api.lootvm.com/v1Chat Completions: POST /v1/chat/completions
Messages (Claude): POST /v1/messages
What not to send
Section titled “What not to send”- Do not place the key in query strings or path segments for these HTTP guides.
- Do not send upstream vendor keys to
api.lootvm.com; configure providers only in the Console as an operator. - Do not reuse browser session tokens or Console access tokens as API keys for relay clients.
Rotate or revoke
Section titled “Rotate or revoke”Revoke or rotate keys from the Console when a secret may be exposed or when access should end. After revocation, clients receive authorization failures until they use a valid key.
Next steps
Section titled “Next steps”- Chat Completions and Messages (Claude) — protocol guides
- Client Integrations — Cursor, Codex, OpenCode, Claude CLI, and other clients