Separate keys for local, staging, and production
2026-05-05 · Billing
One account balance, more than one key, so you can revoke a laptop without stopping the worker.
Create three keys if you have three environments. Name them in the dashboard. The balance is shared, so a runaway test spends production credits. Use a small account or watch the alert.
Revoke a key that was pasted into a ticket. The hash is what the server checks. Deleting it from a chat log does not un-spend it, but revocation stops new calls within half a minute.
The prefix remains visible so the usage makes sense after the secret is gone.
Never put the production key in the sample commands in a README. The samples use an environment variable on purpose.
Ready to call it? Start with the quickstart, the API guide, or pricing.