Leaked Cohere 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 Cohere step below comes from Cohere's own docs, checked 17 Nov 2026.
Free. No sign-up.
What to do now, for Cohere
Revoke the key now
A team owner deletes the key on the API keys page, then creates a new one. Team members who aren't owners can't delete production keys. Do this first: until it's revoked, anyone who copied it can keep spending. GitHub alerts the repo's owner about Cohere keys, and its push protection can block them, but it doesn't report them to Cohere, and Cohere's docs don't say it disables leaked keys.
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.
Check usage for charges that weren't yours
Check the usage and billing table on the dashboard's billing page. Cohere's docs don't say it can filter by key. Note the time the key leaked and the time you revoked it.
Cap what any key can spend
Set a monthly spending limit on the Spending Limit tab of the billing page. Once it's reached, requests fail with a 402 error until next month, or until you raise it. Cohere's docs don't make clear whether it covers the whole account or one key. Production key usage is metered and invoiced.
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.
If someone ran up charges, ask for them back
Email support@cohere.com. Cohere's SaaS agreement asks you to report unauthorised use promptly, and says Cohere isn't liable for any unauthorised use of its products. Say when the key leaked, when you revoked it and which usage wasn't yours.
Checked in Cohere's own docs. Sources: teams and roles, rate limits, FAQ, errors, release notes, 28 Jun 2023, SaaS agreement. 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 Cohere disable a leaked key for you?
GitHub alerts the repo's owner about Cohere keys, and its push protection can block them, but it doesn't report them to Cohere, and Cohere's docs don't say it disables leaked keys. Revoke it yourself either way.
Can I cap what a Cohere key spends?
Set a monthly spending limit on the Spending Limit tab of the billing page. Once it's reached, requests fail with a 402 error until next month, or until you raise it. Cohere's docs don't make clear whether it covers the whole account or one key. Production key usage is metered and invoiced.
How do I see what a leaked Cohere key was used for?
Check the usage and billing table on the dashboard's billing page. Cohere's docs don't say it can filter by key.
Will Cohere refund charges from a leaked key?
Email support@cohere.com. Cohere's SaaS agreement asks you to report unauthorised use promptly, and says Cohere isn't liable for any unauthorised use of its products.
How do I find where my Cohere key leaked?
Search your code, your git history and your live site's JavaScript for the first few characters of the old key. Common places are browser code, a committed .env or local settings file, and screenshots.
Other providers
- Leaked OpenAI key
- Leaked Anthropic key
- Leaked Google Gemini key
- Leaked xAI key
- Leaked Mistral key
- Leaked DeepSeek key
- Leaked OpenRouter key
- Leaked ElevenLabs key
- Leaked Replicate key
- Leaked fal key
- Leaked Groq key
- Leaked Together AI key
- Leaked Hugging Face key
- Leaked Perplexity key
- Which providers stop a leaked key for you
- Security checklist for vibe-coded apps