Kilo Code credits are a prepaid dollar balance that Kilo draws down at the model provider's own rate each time the agent calls a paid model through Kilo Gateway. To see how much of that balance is left next to your other coding tools, connect Kilo Code to UsageAtlas, a free and open-source desktop tracker.
What a Kilo Code credit pays for
Kilo's adding credits page says gateway inference matches the provider's API rates with no markup, and that your credits are debited by whatever inference or other metered services cost. Cloud compute for Cloud Agents comes out of the same balance but is charged separately from inference.
What a session costs depends on the work. Kilo's cost controls page lists the drivers:
- the model you pick, since frontier models cost far more per token
- prompt and context size, including history and attached files
- the number of agent steps and tool calls
- retries, loops and long background tasks
Requests sent with your own provider key (BYOK) cost nothing on Kilo's side; you pay that provider directly. Free models do not touch the balance either.
Three ways to add credits
| Option | How it works | Price |
|---|---|---|
| One-time purchase | Top up from your profile page | Pay as you go |
| Automatic top-up | Buys more when the balance runs low | Pay as you go |
| Kilo Pass | Monthly or annual subscription that adds paid credits plus bonus credits | From $19 a month |
Kilo calls the Pass its most cost-effective option. A processing fee applies to purchases, so check the pricing page for the current terms.
Personal and organization credits are separate pools
This is the part that confuses people most. Kilo's billing FAQ states that credits are not shared between your personal account and an organization. If your credits sit in one and the IDE is using the other, Kilo shows a low balance warning even though you paid.
The fix is to switch environment: the dropdown selector in the IDE, or /teams in the CLI. Organizations draw from one shared pool, and owners can add per-user daily limits on top.
Track Kilo Code credits in UsageAtlas
UsageAtlas shows the remaining Kilo balance on its Limits page, beside Claude Code, Codex, Cursor, Copilot and the other tools it supports.
- Install UsageAtlas on Windows, macOS or Linux.
- Open Settings, then Sources, find Kilo Code and expand Connect.
- Paste a Kilo API key. Leave the organization ID empty for your personal balance, or enter the organization you want to watch.
- Choose Save and check, then open Limits.
If you already ran kilo auth login, UsageAtlas can read that login, or you can set KILO_API_KEY. A saved key wins over both, so remove an old one if it points at the wrong account.
Limits then shows the active credit blocks, the remaining USD balance and Kilo Pass counters when Kilo returns them. Expired or not-yet-active blocks are left out of the current balance.
What the balance can and cannot tell you
A balance is what remains, not what you spent. A top-up raises it and an expiry can lower it without any coding happening. UsageAtlas therefore does not turn balance changes into cost history, and the Kilo connection does not import per-request tokens or models. For invoices and spending history, use Kilo's own Usage page and billing records.
The integration also reads one scope at a time. It will not merge every organization you belong to into one number.
If Kilo Code is your only AI tool, Kilo's dashboard may be all you need. UsageAtlas helps when Kilo is one of several agents and you want every balance and limit in one window.
Price and privacy
UsageAtlas is free and open source under the MIT license. Local tracking needs no account, it does not read prompts or responses, and saved keys stay in your system's encrypted storage. The Kilo Code credits and Kilo Pass guide has the short version.