API keys

Open User → API Keys. API keys (sk-…) authenticate calls to the Proxy: Authorization: Bearer sk-….

The list shows status, last used time, and a read-only budget summary tied to the owning user (so you can sanity-check spend at a glance). When creating a key, choose attach to an existing user or external identity so the wizard can resolve or create the right user (follow the on-screen steps).

Prerequisite

Create a User first, or use external-identity mode in the key wizard.

API Keys shows key status, owning user, and budget summaries. Emails and key fragments are pixelated in this screenshot.

What to do in Admin

1. Open API Keys.
2. Create: follow the wizard → pick or enter user info → set a display name → save and copy the full sk-… immediately (the UI usually warns it is shown only once).
3. Operate: review the list; edit, revoke, or delete as needed.
4. Smoke test: call GET /v1/me on your Proxy base URL with Bearer sk-… and confirm the response matches expectations.

curl -sS "http://localhost:8787/v1/me" \
  -H "Authorization: Bearer sk-your-api-key"

Replace the URL and key with your environment.

Automation

Use the admin HTTP API from trusted servers — see the GitHub technical reference.

Next

• Request logs
• Integration