Keyll · API key abuse protection

Keyll the Gemini key. Not the project.

Keyll watches usage on every API key you connect, on Google Cloud, Anthropic, OpenAI, OpenRouter or Resend, and blocks the one being abused. Every other key keeps working.

The Keyll dashboard overview: one key blocked. maps-website ran at 1,941 requests a minute, 47 times its normal 41, and was blocked while the other keys kept working.

Watches per-key usage on

Gemini API, Anthropic, Maps, OpenAI, Google Cloud, OpenRouter, Cloud Translation, Firebase, Resend.

The cost of a leaked key

The bill is rate times minutes. Attackers set the rate. Keyll cuts the minutes.

Stolen Gemini key
$82,314
billed in two days, Feb 2026
The Register, Mar 2026
Live keys exposed
2,863
Google keys that could call Gemini
Bitdefender, Feb 2026
Burn rate
$28.58
a minute, in that theft
The Register, Mar 2026
Time to a block
~20 min
on Google Cloud, with Keyll's defaults
Monitoring delay + 20 min over the limit
Reported in 2026

Surprise bills, everywhere

A spending cap didn't stop any of them. Each one links to the original report.

  • $82,314

    Gemini API · Mexico · Feb 2026

    A three-person startup's stolen key ran image and text models for two days.

  • $10,000

    Google Cloud · Australia · May 2026

    Billed despite a $250 spending cap.

  • $127,000

    Google Cloud · May 2026

    The account was locked for non-payment, and so were the logs needed to dispute it.

  • $30,000+

    AWS Bedrock · May 2026

    Marketplace charges skip Cost Anomaly Detection, so no alert ever fired.

How Keyll works

One bad key shouldn't take down the rest

A small watcher runs in your Google Cloud project or on your own server, and holds the only credentials. Keyll decides, but the watcher only runs a block that Keyll signed and that fits the limits you set on your side. Key strings never leave your environment.

Traffic chart and keys table: maps-website at 1,941 requests a minute against a normal 41, marked Blocked.
Frequently asked questions

Got questions?

Not yet. The dashboard and the watcher run end to end against an emulator of each provider. Join the waitlist for one email at launch.

On Google Cloud, a custom role with four: read request counts, list and read keys, and update a key's restrictions. It can't read key strings. Anthropic, OpenAI and OpenRouter have no narrower credential, so there the watcher needs an admin or management key. Either way the credential stays where the watcher runs, and Keyll holds none.

It alerts within minutes. On Google Cloud a block lands about 20 minutes in: the provider's reporting delay, 10 minutes of sustained abuse, then a 5-minute warning you can cancel.

You get a warning before each block and can cancel it. After a block, one click undoes it: a Google Cloud key gets back the exact restrictions saved on it, and Anthropic and OpenRouter keys are switched back on. The watcher starts in dry run and blocks at most 3 keys an hour.

Google Cloud keys (Gemini, Maps, Firebase, Vertex AI and the rest), Anthropic, OpenRouter, OpenAI and Resend. OpenAI and Resend keys get alerts unless you opt in to blocks: OpenAI's API doesn't say what a key's permissions are, and Resend can only delete a key. AWS and Supabase are planned.

$15 a month at launch; the waitlist is free. Dispute help is the incident report, CSV and evidence hash plus the steps for a billing case. The refund is the provider's call; Keyll pays nothing out.

Waitlist open

Find out in minutes, not on the invoice

Free to join. $15 a month at launch, with dispute help included. One email when Keyll ships, then we delete the list.

Had a surprise cloud or AI bill?
Would you pay $15 a month for Keyll?
Where do your keys live? Pick any