Keys and authentication
Audience: members and administrators. Creating and managing shared keys is covered in Shared API keys.
Two kinds of key, billed differently
| Personal key | Enterprise shared key | |
|---|---|---|
| Managed in | Console → API keys (/keys) | Console → Shared API keys (/org/tokens) |
| Belongs to | You | The enterprise — not attributed to a member |
| Spends | Your own balance | The enterprise shared balance |
| When the enterprise balance is short | n/a | No fallback to your personal wallet |
| Constrained by | Your own quota and subscription | The key’s own quota |
| Who can create | You | Enterprise administrators |
A shared key does not fall back to a personal wallet. It draws on the enterprise balance, and when that is exhausted the request is rejected rather than charged to the caller. Handing someone a shared key hands them the enterprise balance — set the key’s quota deliberately.
Which side a member’s own calls are charged to is a per-enterprise billing policy: with enterprise billing enabled, calls draw on the enterprise balance, and only when the enterprise allows “personal wallet fallback” does an insufficient enterprise balance fall through to the member’s own balance. Those switches live in Settings.
Authenticating
Following the OpenAI convention:
Authorization: Bearer sk-...| Purpose | Address |
|---|---|
| OpenAI-compatible API | https://alltokens.si/v1 |
| Gateway health check (no key needed) | https://alltokens.si/api/status |
Key states
| State | Meaning | What to do |
|---|---|---|
| Enabled | Usable | — |
| Disabled | Switched off manually; requests are rejected | Re-enable it |
| Expired | Past its configured lifetime | Create a new one |
| Exhausted | Reached its quota | Raise the quota or create a new key |
Hygiene
- A key is money. Never commit it, paste it into chat, or ship it in front-end code.
- Inject keys through environment variables or a secret manager.
- Use a separate key per purpose: one leak then affects one place, and you can tell sources apart in Request logs.
- If you suspect a leak, disable or delete the key immediately and issue a new one.
- The plaintext is usually shown once at creation — save it then.
Related
- Client setup — putting a key into a tool
- Shared API keys — the administrator view
- FAQ — what 401 / 402 / 403 / 429 mean