API keys and usage

API keys let your own code spend your kral credit. The dashboard gives you two tools to keep that under control: per-key limits and a complete usage log.

Creating a key

Under API keys, click New and give the key a name. The plain-text key, starting with sk-kral-, is shown exactly once at creation; store it in your secret manager right then. Afterwards the dashboard only shows the prefix.

The practical pattern is one key per project or environment. When something misbehaves, you can see which key it was and act on just that one.

Per-key spend limits

Each key can carry its own daily and monthly spend limit. At 75 percent of a limit you get a warning, by email and in the dashboard, so you can react before anything stops. At 100 percent, requests on that key are rejected until the day or month rolls over or you raise the limit; the rest of your account is unaffected.

This is the safety net for a bug that loops, or a side project that should never cost more than a few euros. The daily limit is the one that caps the blast radius: a runaway integration can burn a monthly budget overnight, but never more than one day's cap.

Disabling and rotating

Keys can be disabled instantly and re-enabled later, without touching code that holds other keys. To rotate, create the new key first, deploy it, then delete the old one: deletion is immediate and permanent.

The usage log

The Usage page lists every request on your account: timestamp, model, input and output tokens, exact cost, and where it came from. The source column shows the API key's name, or Web for requests made in the chat app. Filter by source or model to see what a project really costs. The same numbers drive your balance, so the log and your credit always agree.

Connecting

Base URL, code samples, and the full endpoint list are in the API quickstart and Endpoints.