API Keys
Automation starts with deliberate access.
Give an application a named credential instead of sharing an interactive login. Create a key, store it securely and keep its lifetime tied to the work it supports.
A key authenticates as your account and is not inherently read-only. Model use still depends on model access, plan rules and credit.
Name it. Protect it. Retire it.
- 01
Create with a purpose.
Give the key a recognisable name and choose an expiry where appropriate. Copy the full key from the creation response.
- 02
Keep it server-side.
Use a secret manager or protected runtime environment. Never commit the key or include it in frontend code and logs.
- 03
Revoke when the work ends.
Remove credentials you no longer need. Revoked or expired keys are rejected on subsequent validation.
Visible management
Know which credentials still have access.
The key list shows metadata rather than the full secret. Keep names meaningful and review the keys used by applications and automation.
Compatibility API
Key count is not an inference allowance.
Starter accounts can have up to five non-revoked keys; Pro, Pro+, Ultra and Team up to ten. Expired but non-revoked keys still count. This does not grant additional model access or credit.
Protect the credential and the model context.
The backend stores a hash of the API key. Your application still needs to protect its copy and review what it sends. Model-processing guarantees do not make leaked credentials harmless.
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
Can I see the full key again later?
Does a key have a required expiry?
Does revocation stop every running stream instantly?
API Keys
Create one key for a clear purpose.
Open API access, name the credential and set a suitable lifetime. Store it securely before connecting your application.
A key authenticates as your account and is not inherently read-only. Model use still depends on model access, plan rules and credit.
Want to start with your team? Talk to us.