Authentication
Public developer traffic to POST /v1/chat/completions is authenticated with a single mechanism: your Rikaii API key in the Authorization header.
API key (inference)
| Item | Value |
|---|---|
| Header | Authorization: Bearer <your-api-key> |
| Where to get the key | Dashboard → API keys — create a key and store it in a secret manager. The plaintext is shown once at creation. |
| Format | Opaque string issued by the gateway (currently rk_live_ plus random characters). Treat it like a password. |
Requirements
- Send
Bearer(with a space) before the key. Malformed headers yield 401. - Use HTTPS only. Do not embed keys in browsers, mobile apps, or public repos.