Warp AI credits are Warp's unit for agent work, and the quickest way to see yours is Settings > Billing and usage in the Warp app. To keep that balance in view next to Claude Code, Codex, Cursor and your other coding tools, connect Warp to UsageAtlas, a free and open-source desktop tracker.
What a Warp credit measures
A credit is not a prompt and not a token. Warp's credits and billing docs call it "a usage unit, not a token or a fixed number of prompts." The same request can cost different amounts on different days, because the price depends on:
- the model you pick
- how much input and output the task produces, and how much is cached
- how many tool calls and summary steps the agent runs
- extras such as web search
So two sessions with the same number of prompts can end with very different balances. That is the main reason people go looking for a tracker: the count of messages tells you little about what is left.
One more detail from the same page: Warp now bills some accounts in dollars and others in credits. Your Billing and usage screen shows which unit applies to you.
Where Warp shows your balance
Warp itself gives you three views:
| View | Where | What it answers |
|---|---|---|
| Account usage | Settings > Billing and usage | Included allowance, purchased balance, reset date |
| Turn usage | Below each agent response | What that one response used |
| Conversation usage | Conversation summary | What the whole thread used |
In the Warp Agent CLI, /usage opens the account panel and /cost shows what the latest response used.
These are good answers inside Warp. They do not help when you are working in another tool and want to know whether a long Warp agent run will fit.
Track Warp AI credits in UsageAtlas
UsageAtlas reads what Warp reports for your account and puts it on its Limits page, beside the other coding tools it supports. Setup takes a minute:
- Install UsageAtlas on Windows, macOS or Linux.
- In Warp, create an API key under Settings > Cloud platform > API keys.
- In UsageAtlas, open Settings > Sources, find Warp and expand Connect.
- Paste the key, choose Save and check, then open Limits.
If you prefer not to save the key, start UsageAtlas with WARP_API_KEY set instead.
On Limits you see monthly use, the reset Warp reports, and any add-on balances. Personal and workspace pools stay apart, so a shared team balance is never folded into your own total. An unlimited allowance shows a used count without an invented percentage, and a limit Warp does not report shows as unknown rather than zero.
You can also set a low-capacity alert for any window with a known allowance. Keep UsageAtlas running in the tray and it warns you before the balance runs dry.
What the Warp connection does not do
The Warp integration reads current allowances and balances. It does not import per-request tokens, models, projects or past spending, and it cannot buy add-ons or raise your allowance. An expiring purchase is not treated as a reset either, since Warp's purchased usage expires 12 months after purchase while included usage renews monthly.
If Warp is the only AI tool you use, its own Billing and usage screen and /usage panel may be all you need. UsageAtlas earns its place when Warp is one of several tools and you want one view for all of them.
Privacy and price
UsageAtlas is free and open source under the MIT license. Local tracking needs no account; a free sign-in only adds cloud saves of your usage history. It does not read prompts or responses, and saved keys stay in your system's encrypted storage, outside cloud saves.
The step-by-step version lives in the Warp credits guide on usageatlas.com.