Learn how to create, manage, and protect API keys for ScitiX Model Inference, including usage limits and access control basics.
API keys authenticate programmatic requests to the ScitiX Model Inference API. Use one key per application or environment so development, staging, and production traffic can be managed independently.
Go to the API Keys page and click Create API Key. Give it a recognizable name, then copy the key and store it in an environment variable instead of hard-coding it:
export API_KEY="YOUR_API_KEY"
Treat API keys like passwords. Never commit them to Git or expose them in client-side code.
Each key supports quotas and rate limits. In shared environments, experiments, or third-party integrations, these settings help you define clear boundaries for cost and throughput.
Quota limit settings: Use a Monthly Quota for the current month or a Total Quota for lifetime spend.
Rate limit settings: Use a TPM Limit (tokens per minute) and an RPM Limit (requests per minute) to control throughput.
Each key provides management actions in the key list:
Edit: Modify the quota limit or rate limit.
Pause: Temporarily block a key without deleting it. This is the safest first step when investigating unexpected usage, because you can re-enable the key later.
Delete: Permanently revoke a key. This cannot be undone. Update any application that still depends on the key before deleting it.
The key list shows each key’s status, last-used time, and monthly token usage. If traffic looks unusual, review your usage trends first, then tighten quotas or rate limits. You can also pause the key while investigating.
