Credits do not count your prompts
Warp's credit guide explains that consumption varies with the work performed. One task can involve several model calls and consume multiple credits. UsageAtlas labels these values as credits; it does not treat them as token counts or raw request history.
Compare monthly and add-on pools separately
The Warp connection reads supported monthly use and allowance, reported reset, and personal or workspace add-on balances. A workspace pool is not added to your personal total. An unlimited allowance does not become an arbitrary percentage just because the used counter is available.
Keep credits visible while you work
Connect your Warp API key to UsageAtlas. Open Limits for current counters and set an alert for supported windows with a known allowance. UsageAtlas is free and open source. It does not increase credits, buy add-ons, or infer past spending from balance changes.
Questions, answered
Is a credit expiry the same as a quota reset?
No. Expiry removes a grant; a reset renews an allowance. UsageAtlas does not turn an expiring bonus into a reset alert.
Why do my credits differ from my number of requests?
Credits are a provider-specific resource unit. A single request can consume more than one credit, so those counts need not match.