Modify Key Settings
After creating a key, you can adjust quota, model access, group, expiration, and other limits. Splitting keys by tool makes usage easier to understand and makes emergency revocation safer.
Common settings
| Setting | Purpose |
|---|---|
| Name | Distinguish clients, tools, or projects |
| Quota | Limit total usage for the key |
| Expiration | Useful for temporary testing or short-term sharing |
| Model restrictions | Allow only selected models |
| Group | Controls pricing, routing, and tool compatibility |
| IP restrictions | Allow calls only from specific egress IPs |
Recommended practice
- Create a separate key for each tool, such as
claude-codeandcodex. - Use short expiration and low quota for temporary tests.
- Use IP restrictions for production services.
- Disable or delete a key immediately if you suspect leakage.
Changes do not take effect
Some clients cache settings. After modifying a key, restart the client or reload its configuration.