Amp Orb credits are hours, and that changes how you plan
Time is a proxy for compute. Useful for access planning, wrong for budgeting spend.
· 2 min read
Amp Orb credits are billed in hours, not dollars, and that single fact explains most of the confusion around Amp's usage pages. Agent work is metered in currency, Orb work is metered in time, and the two pools do not convert into each other without an assumption you would have to invent. The UsageAtlas Amp guide keeps them separate for exactly that reason.
The two pools
| Pool | Unit | What consumes it |
|---|---|---|
| Agent usage | Dollars | Agent requests and model work |
| Orb usage | Hours | Time spent on Orb |
| Workspace credits | Workspace pool | Shared spending by members |
Trying to merge them produces a number that looks authoritative and is meaningless. The UsageAtlas integration takes the honest route and keeps them as separate counters, matching what Amp reports.
Where to read them
Amp's pricing documentation points to the amp usage command and to user or workspace settings. Those are the authoritative sources, and they are the right place to check before starting a long run.
A desktop view can mirror them with an access token:
- Create a token in Amp's settings.
- In the app, open Settings, then Sources, expand Amp and choose Connect.
- Paste the token, save and check, then open Limits.
Thread-level costs are not part of that view. Amp's own thread details remain the place to see what one conversation consumed.
Why hours are a strange unit for compute
Time is a proxy. An hour on Orb costs whatever the work inside it needed, so an hour of idle waiting and an hour of heavy agent loops can differ enormously in underlying spend.
That makes Orb hours useful for planning access rather than for budgeting money. If your constraint is "can I run Orb this afternoon", the hours counter is exactly right. If your constraint is "what did this month cost", it is the wrong counter.
Reading a capacity meter honestly
A meter appears only when the provider reports enough detail. When it does not, the value is unknown, and the app shows it that way rather than as zero.
This matters more than it sounds. Teams that treat an unknown limit as zero cancel work unnecessarily. Teams that treat it as unlimited discover the real limit at the worst moment.
Connecting safely
Saved provider credentials go through the operating system's encrypted storage and stay out of cloud saves. An AMP_API_KEY environment variable works too, and the app needs a restart to pick up a change. No UsageAtlas account is required for local tracking.
What to do when the numbers look wrong
Three checks, in order. Confirm both views refer to the same account. Confirm one is not showing workspace credits while the other shows personal. Confirm no view is summing hours and dollars.
Most discrepancies are the first check. The CLI may be signed into a different account than the browser tab you are comparing against.
FAQ
Can I convert Orb hours into dollars?
Not reliably. The dollar cost of an hour depends on what ran during it, so any fixed conversion is an assumption.
Does the integration import Orb session detail?
No. It reads reported allowances and balances, not per-session history.
Is a missing Orb limit a zero balance?
No. A missing limit means the provider did not report enough information to draw a meter.