For the complete documentation index, see llms.txt. This page is also available as Markdown.

Rotate a provider key

Replace a provider credential without breaking active workloads.

Rotate a provider key by adding its replacement first. Keep the existing key active until requests succeed with the new credential.

Provider keys are resolved at request time. Your application's API Keys do not need changes during rotation.


When to rotate a provider key

  • A provider key has been compromised, or you suspect it has.

  • Your organization has a periodic key rotation policy.

  • You're migrating traffic to a new provider account.


Rotate the key

  1. Create a new API key in your provider's dashboard. Do not revoke the existing key yet.

  2. In otari.ai, select Organization and then Providers.

  3. Click Add provider key. Select the same provider, enter a distinct Key Name, and paste the new API key.

  4. Set the new key as the provider's default by clicking its star icon.

  5. For each workspace that pins the old key, click Edit and select Always use this key for the new key.

  6. Send a test request from each affected workspace. Confirm it completes successfully in the Usage tab.


Remove the old key

Once requests are flowing through the new key, revoke the old key in the upstream provider dashboard.

  1. Return to Organization → Providers in Otari.

  2. Remove the old provider key.

If you suspect compromise, create and assign the replacement immediately. Then revoke the exposed key with the provider.

Last updated

Was this helpful?