Get started

Authentication

Every inference, model-list and usage request is authenticated with an LLMFLUX API key created in your dashboard.

Sending your key

Send the key in the Authorization header as a Bearer token. The Anthropic style x-api-key header is accepted too. If both are present, Authorization wins.

curl https://api.llmflux.dev/v1/models \
  -H "Authorization: Bearer $LLMFLUX_API_KEY"

curl https://api.llmflux.dev/v1/models \
  -H "x-api-key: $LLMFLUX_API_KEY"

Which endpoints need a key

GET /v1/models, GET /v1/usage and every POST inference route require a key. GET /v1 is an unauthenticated discovery and health endpoint.

Authentication errors

No key sent → 401 missing_api_key
Unknown, revoked or deleted key → 401 invalid_api_key
Account not yet verified with Telegram → 403 permission_denied

{
  "error": {
    "message": "API key invalid, expired, or revoked.",
    "type": "authentication_error",
    "code": "invalid_api_key"
  }
}

Keeping keys safe

Treat keys like passwords. Keep them in environment variables or a secret manager, never in client-side code, public repositories or screenshots. The full key is shown only once, when it is created. LLMFLUX stores only a hash. Create and delete keys in the dashboard.