Authentication

Kyara Intelligence authenticates every request with an API key that you send as a bearer token in the Authorization header. There are no sessions or cookies. Each request is authenticated on its own, so keeping your key secret is essential.

Get your key

Create and manage your API keys in the Kyara dashboard. Keys start with kai_. When you generate a new key, it is shown to you only once, so copy it immediately and store it somewhere secure such as a password manager or a secrets vault. If you ever need to rotate a key, you can regenerate it from the dashboard at any time. Regenerating immediately revokes every key on your account, including keys created through the onboarding flow, so update any services using them before you rotate.

Send the token

Pass your API key in the Authorization header as a bearer token on every request. The value must be the string Bearer followed by your key.

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!" }
    ]
  }'

If you’re using the OpenAI JavaScript or Python SDK, you don’t need to set the header manually. The SDK does it for you when you supply your key through the apiKey parameter:

const client = new OpenAI({
  baseURL: "https://api.kyara-intelligence.com/v1",
  apiKey: process.env.KYARA_INTELLIGENCE_API_KEY, // SDK sets the Authorization header for you
});

Never hard-code your API key in client-side code or commit it to a repository. Always read it from a server-side environment variable named KYARA_INTELLIGENCE_API_KEY. Exposed keys can be used by anyone to run requests at your expense.

Let users bring their own key

If you’re building an application for other people, use the hosted onboarding flow instead of collecting keys manually. Send users to:

https://kyara-intelligence.com/onboard?redirect=<your-redirect-url>

Kyara guides the user through creating their own API key, shows it to them once, and then sends them back to your app through the redirect URL. The key is not appended to the redirect, so the user copies it and pastes it into your app to finish connecting. This keeps your users in control of their own credentials. See the onboarding API reference for full details on the redirect parameter and the flow.

Error reference

Errors use the OpenAI error envelope: { "error": { "message", "type", "param", "code" } }.

HTTP status	`type`	`code`	Cause
`401`	`authentication_error`	`invalid_api_key`	The `Authorization` header is missing, or the key is not recognized (revoked or mistyped).
`400`	`invalid_request_error`	`null`	The `Authorization` header is present but malformed, for example a scheme other than `Bearer` or an empty token.
`403`	`permission_error`	`no_active_plan`	The key is valid but the account has no active subscription and no top-up credits, for example after a failed payment.

If you receive a 401, check that the key has not been regenerated or deleted in the dashboard. If you receive a 400 on a request you expect to authenticate, check that the header is formatted exactly as Bearer <key>. If you receive no_active_plan, subscribe or fix the payment method in the dashboard. Top-up credits you already own keep requests working without an active subscription.

Get Started

Integrations

API Reference

Reference

Get your key

Send the token

Let users bring their own key

Error reference

​Get your key

​Send the token

​Let users bring their own key

​Error reference

Get your key

Send the token

Let users bring their own key

Error reference