One page. One job.

Tell you whether an AI API key works, who it belongs to, and how much is left. Then forget it.

Why it exists

Anyone building with AI ends up with a drawer of keys. Old ones, team ones, ones from a trial that ended in March. To test one you open a terminal, look up the right curl command, and read a wall of JSON.

That is a thirty second job that takes five minutes. This is the thirty second version.

How it works

We look at the shape of the key and guess the provider. sk-ant- is Anthropic. AIza is Google. gsk_ is Groq. Then your browser calls that vendor's cheapest read endpoint with your key and we read the answer.

If the vendor has an endpoint that reports credit, we show the number. If it does not, we say so instead of guessing. Most do not.

What we will not do

We will not store keys. Not encrypted, not hashed, not for a minute. The moment a tool keeps keys it becomes a target, and the promise on the front page becomes a lie.

So there is no server side. The whole checker is a static page and a JavaScript file you can read.

How it pays for itself

Ads and hosting costs. Nothing else. We do not sell data because we do not have any to sell.

Roadmap

• More providers as people ask for them.
• Bulk check for a list of keys, still in the browser.
• A rate limit read where vendors return one in headers.
• A copy button for a curl command, for people who want to check it themselves.

Say hello

Missing provider or wrong verdict? Mail hello@aicheck.in with the provider name. Never send the key.