← Field notes

Guide

Rotate an API key without stopping a workload

Replace a key safely and keep each app’s budget and usage visible.

Create the replacement first

Identify the caller and current key label in Usage. Create a replacement with an identifiable name and set its daily cap, lifetime budget and expiry. Copy the secret to your secrets manager when the console displays it.

Verify the deployment

Update the caller’s secret and redeploy it. When live inference is available, send a small request and review its status and key label in Usage. Roll back the caller configuration while both keys are valid if the replacement fails.

Revoke the old key

Revoke the old key once every caller uses its replacement. If a key has been exposed, revoke it immediately, then review requests and charges for its label.

Key management guide ↗