Get started
Authentication
Every request carries an API key as a bearer token. Create a key, send it, and keep it secret.
Kyara Intelligence authenticates each request on its own, from the bearer token in its Authorization header. There are no cookies or logins on the API, so whoever holds a key can spend from your account. Keep it
secret.
Get your key
Create your key on the dashboard overview with Generate API key. Keys start with kai_. A new key is shown only once, so copy it into a password manager or secrets vault right away.
Regenerating a key
Click Regenerate on the dashboard to replace a lost or leaked key. Regenerating issues one new key and immediately revokes every key on your account, including keys created through the onboarding flow, so update the services that use them first.
Send the token
Send Authorization: Bearer followed by your key on every request:
curl https://api.kyara-intelligence.com/v1/chat/completions \
-H "Authorization: Bearer $KYARA_INTELLIGENCE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek/deepseek-v4-flash",
"messages": [
{ "role": "user", "content": "Hello!" }
]
}'With the OpenAI SDKs you don't set the header yourself. Pass the key as apiKey (api_key in
Python) and the SDK sends it:
import OpenAI from 'openai';
const client = new OpenAI({
baseURL: 'https://api.kyara-intelligence.com/v1',
// The SDK sends this as the Authorization header for you.
apiKey: process.env.KYARA_INTELLIGENCE_API_KEY
});Keys for your users
If you build an app for other people, let each user bring their own Kyara account instead of sharing yours. Their usage then runs on their own plan and credits. There are two ways to set that up:
- Onboarding flow: a hosted page where the user signs in, creates their own API key, and returns to your app to paste it.
- OAuth: the user approves your app once, and your app receives
short-lived access tokens. The API accepts them in the same
Authorizationheader as a key.
Authentication errors
Errors use the OpenAI error envelope. Errors lists every code.
| Status | type | code | Cause |
|---|---|---|---|
401 | authentication_error | invalid_api_key | The Authorization header is missing, or the token isn't recognized: a mistyped, revoked or
regenerated key, or an expired OAuth access token. |
400 | invalid_request_error | null | The header is there but malformed, for example a scheme other than Bearer or an empty token. |
403 | permission_error | no_active_plan | Chat completions only. The key is valid, but the account has no active plan and no top-up credits, for example after a failed payment. |
503 | server_error | service_unavailable | The token couldn't be checked right now. Retry with backoff. |
On a 401, check that the key wasn't regenerated in the dashboard. On a 400, check that the
header reads exactly Bearer <key>. On no_active_plan, subscribe or fix your payment
method from the dashboard. Top-up credits you already own keep requests
running without a plan.