Skip to content

Leaked Replicate API key? What to do now

Revoke it first, then check what it was used for, cap what your keys can spend and clean up where it leaked. Every Replicate step below comes from Replicate's own docs, checked 15 Nov 2026.

Free. No sign-up.

Whose key leaked?
Where did it leak?

What to do now, for Replicate

  1. Revoke the key now

    Disable the token on the API tokens page, then create a new one. Do this first: until it's revoked, anyone who copied it can keep spending. Replicate disables tokens found in public GitHub repos and emails you.

    Replicate API tokens

  2. Keep the new key on the server

    Put the new key only in a server-side secret: your host's environment settings, your builder's secrets, or Supabase function secrets. Never in a variable starting NEXT_PUBLIC_, VITE_ or EXPO_PUBLIC_, which are sent to every visitor.

    Lovable secretsBolt secretsSupabase function secrets

  3. Check usage for charges that weren't yours

    Check what was spent on the billing page. Note the time the key leaked and the time you revoked it.

    Replicate billing

  4. Cap what any key can spend

    On prepaid credit, new work stops starting once the credit runs out, unless auto reload is on. There's no separate spend limit setting.

    Replicate billing

  5. Clean up the repo, after revoking

    Remove the key from the code and the git history, but only once it's revoked: anyone who cloned the repo, or a fork, still has it. Then turn on push protection, so GitHub blocks the next key you try to push.

    GitHub: removing sensitive dataGitHub: push protection

  6. If someone ran up charges, ask for them back

    Contact Replicate's support. Credit isn't refundable, and there's no stated policy on usage from leaked tokens. Say when the key leaked, when you revoked it and which usage wasn't yours.

Checked in Replicate's own docs. Sources: API tokens, prepaid credit. Dashboards move, so if a link is out of date, look for the same setting under account or organisation settings.

Then find every other copy, with your coding agent

Find every place an API key or other secret is exposed in this project, and fix it. Search the code, env files, config and local settings files (such as .claude/settings.local.json), the full git history (with gitleaks or a similar scanner) and the built browser bundle. Flag any secret in a variable with a public prefix such as NEXT_PUBLIC_, VITE_ or EXPO_PUBLIC_, and any AI provider called from browser code. Move every AI call into a server route or function that reads its key from a server-only variable, add .env and local settings files to .gitignore, and list each key that was exposed and where, so I can revoke it. Don't rewrite git history.

Questions

Does Replicate disable a leaked key for you?

Replicate disables tokens found in public GitHub repos and emails you. Revoke it yourself either way.

Can I cap what a Replicate key spends?

On prepaid credit, new work stops starting once the credit runs out, unless auto reload is on. There's no separate spend limit setting.

How do I see what a leaked Replicate key was used for?

Check what was spent on the billing page.

Will Replicate refund charges from a leaked key?

Contact Replicate's support. Credit isn't refundable, and there's no stated policy on usage from leaked tokens.

How do I find where my Replicate key leaked?

Search your code, your git history and your live site's JavaScript for “r8_” (how Replicate keys start). Common places are browser code, a committed .env or local settings file, and screenshots.

Other providers