# Leaked API keys

[RightNow AI](https://www.rightnowai.co/) / [Decision model](https://www.rightnowai.co/docs/decision-model) / [Leaked API keys](https://www.rightnowai.co/docs/decision-model/leaked-api-keys)

Updated 2026-11-12

Revoke the exposed RightNow decision model API key, replace it in your apps, then verify the replacement.

**Illustration of key recovery.**

```text
[ Exposed key ]
       |
       v
[ Revoke key ]
       |
       v
[ Create replacement ]
       |
       v
[ Update server environment ]
       |
       v
[ Deploy and verify ]
```

Revoke the exposed key, replace it, then verify your app.

## If you find a leak

Open API keys in the console and revoke the exposed key.

Automatic leaked-key reports are not enabled. Revoke a key yourself if it may have leaked.

## Replace the key

1. Create a replacement under API keys and copy it when it appears.
2. Update the app's secret configuration for `SYSTEM_ZERO_API_KEY`.
3. Redeploy the app and run the [example](https://www.rightnowai.co/docs/decision-model/quickstart) with the replacement key.

The full key appears when it is created. The browser tab where you created it temporarily keeps it in memory for your first call. Reloading, leaving the console or signing out clears it. If you lose it, revoke it and create another.

## Prevent leaks

Keep keys out of browser code, public repositories and shared files. Use a separate key for each app so a revoke affects the intended app.

If you need help with workspace access, [contact support](https://www.rightnowai.co/docs/decision-model/support).

Next: Check the [key refusals](https://www.rightnowai.co/docs/decision-model/authentication#refusals) if the replacement request fails.

## Next

[Text caching](https://www.rightnowai.co/docs/decision-model/caching)