FREE SCAN — 150 founder credits, no card

Scan Your App for Exposed API Keys

Scan your app for leaked API keys, tokens, and secrets.

What Is Exposed API Keys?

Exposed secrets are one of the most common — and most damaging — vulnerabilities in modern web apps. An API key, database URL, or service token that ships to the browser, gets committed to a public repo, or sits in a readable config file can be extracted in seconds. With it, an attacker can run up your cloud bill, read your database, send mail as you, or pivot deeper. Minification and obfuscation do not protect secrets; only keeping them server-side does.

How Exposed API Keys Shows Up

Secrets in the client bundle

Keys compiled into frontend JavaScript (e.g. NEXT_PUBLIC_/build-time vars) are visible to anyone who opens DevTools.

Committed to version control

.env files, master.key, and hardcoded tokens pushed to git remain in history even after deletion, and public repos are scraped automatically.

Service keys that bypass everything

A leaked Supabase service_role key or cloud root credential grants full access regardless of your app-level rules.

Third-party token abuse

Leaked Stripe, OpenAI, Twilio, or webhook tokens let attackers spend your money or impersonate your services.

How the Sable Scan Detects It

Live bundle scanning

We scan your served JavaScript and API responses against 100+ secret patterns and flag the exact key and location.

Exposed config detection

We test for publicly reachable .env, config, and credential files.

Validated, not guessed

Findings are confirmed by an agent so you get real leaks with remediation, not regex false positives.

Check Your App for Exposed API Keys

Create a free account and let the agents test your app. Every finding is validated with a proof-of-concept and remediation. 150 founder credits, no credit card.

Get 150 Free Credits

Frequently Asked Questions

Are minified API keys safe in frontend code?
No. Minification only compresses code; the values are still readable in the browser. Any key in a client bundle can be extracted in seconds. Keep secrets on a backend the client calls. Sable scans your live bundle and reports exactly which key is exposed.
I deleted a key from git — am I safe?
Not until you rotate it. Git history retains deleted secrets, and public repos are scraped within minutes of a push. Always rotate any key that was ever committed. Sable helps confirm whether exposed keys are still live.
Is the security scan really free?
Yes. The Headers Scan runs instantly with no signup. For the full agent scan you create a free account and get 150 founder credits with no credit card required — enough to run real scans against your app on demand. Paid credit packs and monthly tiers exist for continuous testing, but you can start for free.
How does Sable scan my app?
Sable runs autonomous pentesting agents (pen-scout, pen-recon, pen-triage, pen-fixer, pen-compliance) that map your attack surface, test against the OWASP Top 10, validate every finding with a proof-of-concept, and re-test after you ship a fix. You chat with the agents on demand instead of waiting weeks for a manual engagement.
Will the scan break or slow down my production app?
No. Scans are designed to be safe and non-destructive. We demonstrate impact with proof-of-concept evidence rather than causing damage, and we never exfiltrate or alter your data.

Scan for Other Vulnerabilities