Limits, groups and expiry
Find the key by name in API keys, then use Edit or its row actions.
Balance is available, but requests fail
Check in this order:
- Is the key enabled?
- Has it expired?
- Does the key have remaining quota?
- Does its group support the requested model?
- Do model restrictions and IP allowlists permit this request?
An unlimited key limit only removes that key's individual cap. Account balance, group permissions and other restrictions still apply.
Before changing groups
Check the target group's models and prices in the marketplace. Different groups may have different availability or billing rules. Recheck the model configured in your client after switching.
Keep your first setup simple. Use automatic grouping or cross-group retries only if needed and available. Refer to actual usage records for final charges.
Disable, delete or replace
| Action | When to use it |
|---|---|
| Disable | Temporarily stop requests while retaining the key configuration |
| Delete | Stop using a key permanently; the original key cannot be restored |
| Create and replace | Rotate credentials or replace a potentially exposed key |
For routine rotation, create and test the replacement before disabling the old key. If you suspect a leak, disable the old key first.
Separate keys by purpose
Use different keys for chat clients, development and production. This lets you stop one application independently and trace usage by key name.