Shared API keys
Path: /org/tokens
Audience: owners and administrators. Members can view this page but not change it. The member-facing comparison is in Keys and authentication.
How it differs from a member’s personal key
| Personal key | Enterprise shared key | |
|---|---|---|
| Spends | The member’s own balance | The enterprise shared balance |
| Attribution | A member | The enterprise — not attributed to any member |
| Personal wallet fallback | n/a | None — an exhausted enterprise balance means rejection |
| Constrained by | The member’s quota and subscription | The key’s own quota |
A shared key spends the enterprise balance and never falls back to the caller’s wallet. Handing one out transfers spending power over the enterprise balance. Set the key quota deliberately and watch consumption in Usage.
Creating a key
Creation requires a quota — the ceiling that key may consume. The plaintext is normally shown once; save it then and pass it to whoever needs it.
Key states
| State | Meaning |
|---|---|
| Enabled | Usable |
| Disabled | Switched off manually; requests rejected |
| Expired | Past its configured lifetime |
| Exhausted | Reached its quota |
Enabling, disabling and deleting
- Disable — the key stops working immediately, the record remains, and you can re-enable it. Prefer this when you suspect a leak: it is faster than reissuing and does not affect other keys.
- Delete — removes it from the list. Only for keys you will not use again.
Who is using these keys
Shared-key calls are not attributed to a member, so they do not appear in per-member usage. To audit shared-key spend, use:
- Usage — enterprise-wide by day / by model;
- Request logs — individual requests with type filters;
- Balance and ledger — every balance change, exportable.
To be completed: a per-key usage breakdown. The console currently has no “by key” aggregation; it can only be inferred from request logs.
Related
- Keys and authentication — how to authenticate
- Audit records — key creation, enable/disable and deletion