API keys and access
Authentication, quotas, expiration and IP restrictions.
Create a separate key for each application so you can set its limits and disable it independently. Review its routing strategy, expiration, quota and IP restrictions before use.
Account balance and key quota are different
Usage is paid from available account credits. A key quota limits how much that key can spend; unlimited key quota does not add account credits.
- Use Authorization: Bearer YOUR_API_KEY for OpenAI-compatible requests. Messages requests can use x-api-key with anthropic-version.
- An IP allowlist must contain the public outbound IP of the device or server making the request. Moving to another network can change that IP.
- Model access depends on the account, routing group and key settings. A model appearing in the public catalog does not grant every key access to it.
- If a key is exposed, disable or delete it, create a replacement, update your applications and review request logs for unexpected usage.