API keys

Key settings

Setting	Effect
Name	A label, 1 to 255 characters
Credit limit	The most this key may spend, in credits. Requests past it fail with `403 credit_limit_exceeded`
Expiry	After this time the key fails with `401 expired_api_key`
Enabled	A disabled key fails with `401 disabled_api_key` until you enable it again
Default routing strategy	The routing strategy for requests that do not name one. Only through the API

There is no rotate action. To rotate a key, create a new one, move your clients to it, then delete the old one.

In the dashboard

On API Keys, Create API Key asks for a name, an optional credit limit and an expiry. The expiry is never, 7, 30 or 90 days, or a date you pick. The new key is shown once. The table lists each key’s usage against its limit, and the row menu renames, sets the limit or expiry, disables, enables or deletes it.

Through the API

The account API needs a provisioning key.

Operation	Request
List keys, newest first, including disabled and expired ones	`GET /v1/account/keys`
Create a key	`POST /v1/account/keys`
Get one key	`GET /v1/account/keys/{key_id}`
Change a key	`PATCH /v1/account/keys/{key_id}`
Delete a key	`DELETE /v1/account/keys/{key_id}`, returns `204`

Create a key

import os
import requests

response = requests.post(
    "https://api.naga.ac/v1/account/keys",
    headers={"Authorization": f"Bearer {os.environ['NAGAAI_PROVISIONING_KEY']}"},
    json={
        "name": "ci-worker",
        "credit_limit": 25,
        "expires_at": "2026-12-31T00:00:00Z",
        "default_routing_strategy": "reliability",
    },
)
response.raise_for_status()
created = response.json()
print(created["id"], created["key"])

const response = await fetch("https://api.naga.ac/v1/account/keys", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.NAGAAI_PROVISIONING_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    name: "ci-worker",
    credit_limit: 25,
    expires_at: "2026-12-31T00:00:00Z",
    default_routing_strategy: "reliability",
  }),
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const created = await response.json();
console.log(created.id, created.key);

curl https://api.naga.ac/v1/account/keys \
  -H "Authorization: Bearer $NAGAAI_PROVISIONING_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "ci-worker", "credit_limit": 25, "expires_at": "2026-12-31T00:00:00Z", "default_routing_strategy": "reliability"}'

Only name is required. The response carries the secret in key, and no later response shows it again:

{
  "id": 38933,
  "name": "ci-worker",
  "key": "ng-...",
  "created_at": "2026-09-26T08:21:55",
  "expires_at": "2026-12-31T00:00:00",
  "is_enabled": true,
  "credit_limit": 25.0,
  "default_routing_strategy": "reliability",
  "message": "Store this key securely. It will not be shown again."
}

Times are UTC without an offset. expires_at must be in the future.

Change a key

PATCH changes only the fields you send. Send null to clear credit_limit, expires_at or default_routing_strategy. name and is_enabled cannot be null.

curl -X PATCH https://api.naga.ac/v1/account/keys/38933 \
  -H "Authorization: Bearer $NAGAAI_PROVISIONING_KEY" \
  -H "Content-Type: application/json" \
  -d '{"is_enabled": false, "credit_limit": null}'

A key_id that does not exist on the account returns 400 with API key not found.

Get started

How NagaAI works

Features

API guides

Account

Product

Key settings

In the dashboard

Through the API

Create a key

Change a key

​Key settings

​In the dashboard

​Through the API

​Create a key

​Change a key

Key settings

In the dashboard

Through the API

Create a key

Change a key