Agent usage and Orb time use different units
Amp's usage documentation distinguishes model and tool spending from Orb usage. An Agent allowance is not interchangeable with compute hours. In UsageAtlas, read the unit beside each counter before comparing it with another pool.
Check the balance attached to your work
Personal and workspace balances can coexist. UsageAtlas displays them independently, along with supported Free or Agent allowances. The integration does not add all balances together or reconstruct thread costs from the amount remaining.
Track the available allowance
Connect an Amp access token to UsageAtlas to keep these counters next to your other tools. It is free and open source. Known allowances can produce capacity meters; exact resets appear only when supported. A rounded renewal estimate is not a precise reset clock.
Questions, answered
Where do I find the cost of a specific thread?
Use Amp's own thread cost details. UsageAtlas's Amp integration currently reads account allowances and balances, not per-thread cost history.
Do unused dollars tell me how many Orb hours I have?
No. Use the separate Orb allowance. UsageAtlas does not convert dollar balances into hours.