Authentication

The Kilo AI Gateway supports multiple authentication methods depending on your use case.

API key authentication

The primary authentication method is a Bearer token passed in the Authorization header:

Authorization: Bearer <your_api_key>

API keys are JWT tokens tied to your Kilo account. See how to get your API key for step-by-step instructions.

Using your API key

{% tabs %} {% tab label="TypeScript" %}

import { createOpenAI } from "@ai-sdk/openai"

const kilo = createOpenAI({
  baseURL: "https://api.kilo.ai/api/gateway",
  apiKey: process.env.KILO_API_KEY,
})

{% /tab %} {% tab label="Python" %}

from openai import OpenAI

client = OpenAI(
    api_key=os.getenv("KILO_API_KEY"),
    base_url="https://api.kilo.ai/api/gateway",
)

{% /tab %} {% tab label="cURL" %}

curl -X POST "https://api.kilo.ai/api/gateway/chat/completions" \
  -H "Authorization: Bearer $KILO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "anthropic/claude-sonnet-4.5", "messages": [{"role": "user", "content": "Hello"}]}'

{% /tab %} {% /tabs %}

Organization tokens

When making requests on behalf of an organization, include the organization ID in the request header:

X-KiloCode-OrganizationId: your_org_id

Organization tokens are scoped with a 15-minute expiry and enforce the organization's policies, including model allow lists, provider restrictions, and per-user spending limits.

Anonymous access

The gateway allows unauthenticated access for free models only. Anonymous requests are identified by IP address and are subject to rate limiting (200 requests per hour per IP).

Free models include models tagged with :free in their model ID, such as minimax/minimax-m2.1:free and z-ai/glm-5:free.

Bring Your Own Key (BYOK)

BYOK lets you use your own provider API keys with the Kilo AI Gateway. When a BYOK key is configured, requests are sent to the provider using your key. You are billed directly by the provider -- Kilo does not add any markup.

Supported BYOK providers

How BYOK works

1. Add your provider API key in the Kilo dashboard or through your Kilo Code extension settings
2. Keys are encrypted at rest using AES-256 encryption
3. When you make a request for a model from that provider, the gateway automatically uses your key
4. Usage is tracked but not billed to your Kilo balance (cost is set to $0)
5. If your BYOK key fails, the request will not automatically fall back to Kilo's keys

BYOK keys can be configured at the personal level or at the organization level. Organization-level keys apply to all members of the organization and require owner or billing manager access to manage.

Request headers

The gateway accepts the following headers: