Authentication

The Draven AI API authenticates every request with a Bearer API key sent in the Authorization header.

Authorization: Bearer sk-drv-<64 hex characters>

API keys always start with the sk-drv- prefix, followed by 64 hexadecimal characters of random entropy. The full key is only ever shown once, at creation time under Developers → API on dravenai.lat — only its hash is stored afterwards, so it can't be recovered if you lose it.

Example request

curl https://api.dravenai.lat/v1/chat/completions \
  -H "Authorization: Bearer sk-drv-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "your-model-id",
    "messages": [
      { "role": "user", "content": "Hello, what is Draven AI?" }
    ]
  }'

Sign of an invalid or missing key

Requests without a valid Authorization: Bearer header, or with a key that doesn't resolve to an active user, are rejected with 401 and authentication_error:

{
  "error": {
    "message": "Incorrect API key provided. You can generate a new one in the console.",
    "type": "authentication_error",
    "param": null,
    "code": null
  }
}

Keys belong to a user, not an app

All the API keys on your account draw from the same rate-limit and token budget (see Rate Limits). Creating more keys doesn't give you more quota — it's meant for separating keys by environment or project, e.g. one for local development and one for production, with independent revocation.