Which of your AI accounts can you actually use right now?

It reads how much of each AI subscription limit you have used, every couple of minutes, and keeps a history. Claude reports a session (5-hour) and weekly window plus per-model windows, Codex reports plan limits, and OpenRouter and Tavily report credit balances. quotamate puts all of them on one page with charts, and lets a team see each other's remaining headroom.

No. The endpoints that report limits are metadata endpoints. They do not run a model and do not count against any quota. Polling every two minutes costs you nothing.

No. quotamate runs in the browser. For Claude and Codex you approve access on the provider’s own sign-in page; for OpenRouter and Tavily you paste an API key.

Yes, for the providers that report money or credits rather than a percentage. Pick last 24 hours, last 7 days, month to date, 30 or 90 days, and quotamate totals what was consumed in that range from its own history. For OpenRouter that answers "what have I spent this month" as opposed to "what is my balance now", which are different questions people ask at different times.

A background sweep reads every connected account roughly every two minutes. The page also has a Refresh button that reads immediately, and the dashboard updates itself while it is open.

Encrypted with AES-256-GCM in our database, under a key derived separately for each account, and bound to the specific row so a ciphertext cannot be moved. They are never sent to your browser and never appear in logs.

No. Sharing an account into a space shares its usage: the provider, plan, meters, history and who owns it. The credential itself is never shared and ownership never transfers. Unsharing removes the visibility immediately.

Only the server, and only to read your usage. Every single decryption is recorded, including failed ones, with the account, who triggered it and why. The code is written so that reading a credential without writing that record is not possible.

Being straight with you: an attacker with both the database and the master key could decrypt stored credentials. Per-account key derivation limits what a single leaked derived key exposes and makes rotation and deletion practical, but it is not a substitute for a managed key service, which is on the roadmap and is not in place today. If that risk is unacceptable for your account, do not connect it.

It does not have to. An inference key shows your per-key limit and spend, and that is the default. Account-wide credits need a management key, and an OpenRouter management key can create and delete every API key in your account. So we put it behind a disclosure and say plainly what it can do.

Yes. Removing an account deletes its stored credential and its usage history. To be precise about what that is and is not: the row and its ciphertext are deleted, which is deletion in the ordinary sense. It is not cryptographic erasure, because the key is derived per user rather than per account, so it is not destroyed by removing one of them.

OpenRouter and Tavily are documented public APIs. Claude and Codex are not. The endpoints their own CLIs use to display your remaining limits are undocumented, and quotamate reads those same ones. They are read-only and change nothing about your account, but the providers can change or remove them without notice.

The affected account stops updating and is marked on the dashboard as needing attention. Nothing is corrupted and no other provider is affected. We fix it and it resumes.

Because there was no data for that period. Drawing a line through it would invent a trend across exactly the hours we know nothing about, so the line breaks instead. A gap means the collector missed those readings, not that usage was zero.

It samples usage every couple of minutes and fits a line through the recent points to get a burn rate in percent per hour, then projects that forward to the ceiling. If the window is flat or falling it reports no date rather than inventing a far-future one, and if there are too few samples it says the confidence is low instead of printing a date you would trust. A window projected to run out before it resets is the case worth acting on, and it is called out at the top.

Because a percentage on its own cannot tell you whether you will make it. A 92% weekly window with an hour left before it resets is fine. A 60% one climbing fast will hit the wall on Wednesday. quotamate flags on the projection, not on a fixed threshold, which is why the two can rank in that order.

How far through that window you are in time. If the bar is well ahead of the tick, you are consuming faster than the window refills and will run out early. It is the difference between a number and a prediction.

A space is a shared view. You invite people, and anyone can share their own accounts into it. Members see each shared account's plan, meters, history and owner. Accounts sort worst-first and anything past 80% or failing to report is called out at the top.

No. Only the owner of an account can share it, and only into a space they are a member of. Being in a space gives you no ability to expose anyone else’s account.

Yes. An organization rolls up every space inside it: which team is closest to a limit, how many accounts are at risk, and which providers you actually run on. A subscription shared into three spaces is counted once, so the org view does not overstate your capacity. You only see spaces you are a member of , being an org admin is about billing and identity, not a key to everyone else's usage.

An organization holds people and billing. A space, which is a team, is a working group inside it with its own shared accounts. Everyone also gets a personal organization at signup, which is private, free forever, and where your accounts live until you share them.

Not yet, and not for want of trying. The consumer Gemini subscription exposes no machine-readable usage at all, and AI Studio API keys have no per-key usage endpoint, so you discover exhaustion by receiving a 429. There is a usable path via Google’s Code Assist internals, but it is fragile and Google has already broken it once. We would rather ship nothing than a number that is quietly wrong.

No, because there is no balance API to read. We probed sixteen candidate endpoints against working controls and found nothing. We could estimate spend from the tokens we observe, but that misses dedicated endpoints, fine-tuning, top-ups and refunds. It would be a guess wearing the costume of a balance.

Ollama Cloud is supported. It is a paid hosted subscription with 5-hour and weekly limits, the same shape as Claude, and quotamate tracks both. Local Ollama is a different thing that happens to share the name: it runs on your machine, has no account and no quota, so there is nothing to run out of and nothing for a hosted dashboard to reach. Connect an Ollama Cloud key from ollama.com/settings/keys; local Ollama needs nothing.

Providers where a real usage or balance endpoint exists and the number can be trusted. If we cannot verify it against a live response, it does not ship.

Individual use is free permanently. Teams will be $2 per member per month and organizations $5 per member per month. Nothing is charged during the beta, including team features, and you will be asked before that changes.

The product works and is in daily use, but it depends on some undocumented provider endpoints, and the security model has one more step to take: a managed key service. We would rather say both up front than wait to be asked.