Get an API key

API keys are created in the console. The CLI never mints its own key — issuance lives behind a real Supabase session so the console UI can guard it.

1. Sign up & finish onboarding

1. Visit console.olava.dev and sign in.
2. Pick a monthly spend cap (between $1 and $10,000). The cap is a hard ceiling; the API will refuse calls that would push your month-to-date spend past it. See Spend cap.
3. Complete Stripe Checkout to attach a payment method. You get a free credit grant (default $25) that burns down before any paid spend.

Until onboarding is finished — payment method attached and a spend cap selected — every metered call returns 402 with code onboarding_incomplete.

2. Mint a key

In the console, Settings → API Keys → New key. You'll see the secret once:

olv_sk_<8-char-public-prefix><opaque-secret>

The 8-character prefix after olv_sk_ is what shows up in the keys list and in our rate-limit logs. The remainder is the secret — store it somewhere safe; we hash it at rest and cannot show it to you again.

The "playground-default" key is auto-created for the console playground. It cannot be revoked through the API (the chat path would just recreate it). Revoke your own named keys instead.

3. Use it

Pass the key as a Bearer token:

curl https://api.olava.dev/v1/me \
  -H "Authorization: Bearer olv_sk_..."

Response:

{ "id": "00000000-0000-0000-0000-000000000000", "email": null }

email is null for API-key auth; we don't surface it on this path.

Next

• Make your first chat call
• List & revoke keys via the API