One key per environment
Separate dev, staging and production. Revoking a leaked staging key should not stop production.
Search sections across the site.
Your keys, usage and plan, in one place.
No account yet? Signing in with Google or GitHub creates one on the Free plan. No card.
One key per environment. Revoking one never touches the others.
Counted against your plan's ceilings.
Link both and either one gets you in.
We cannot email you a lost key, because we never had it.
Separate dev, staging and production. Revoking a leaked staging key should not stop production.
Create the new key first, deploy it, then revoke the old one. Both work in the meantime.
A revoked key returns 401 on its next request. There is no grace period to wait out.
Keys belong in the Authorization header. URLs end up in logs, proxies and browser history.
The panel above is convenience. Automation uses the same four calls.
POST /accounts
{ "email": "you@company.com",
"tier": "free" }
Returns the account and its first key. This is the only response that ever contains the key.
POST /me/keys
GET /me/keys
The list shows each key's id, label and creation date — never the key itself.
DELETE /me/keys/{keyID}
Do this first and ask questions afterwards. Then issue a replacement.
GET /me
GET /usage
/me tells you which account a key belongs to; /me/usage tells you what is left, and is free of quota.
50,000 labels every month with no card on file. It is a plan, not a trial window.
Payment is handled entirely by Stripe. Our servers see the outcome, never the number.
A checkout link is not an upgrade — the plan changes once Stripe confirms payment. Check GET /me to see which tier is actually active.
Comparing plans first? See pricing and limits