Use the account API-key endpoints when you need to manage inference keys programmatically.
This is the right workflow when you want separate keys for production, staging, development, CI, or customer-specific workloads.
Authentication reminder
These endpoints require your provisioning key, not a standard inference key.
Create A Key
The create response includes the plaintext key once. Store it immediately.
API keys are only shown in plaintext once at creation time. Store them
securely right away.
Other Operations
Practical Patterns
Environment Separation
Create separate keys for:
- production
- staging
- development
- testing or CI
This makes usage attribution and incident response simpler.
Budget Control
Use credit_limit to cap how much a key can spend. This is useful for:
- sandbox environments
- short-lived experiments
- customer-isolated workloads
Key Rotation And Revocation
- disable or update keys when rotating credentials
- delete keys that are no longer needed
- remember that deleting a key is irreversible for any client currently using it
Common mistakes
- using a normal API key instead of a provisioning key
- forgetting to store the plaintext key at creation time
- sharing one key across unrelated environments when you need clear attribution
Related Reference Pages