Amp agent credits and workspace balance

The pools

When the number looks wrong

• You are signed in to a workspace and reading your personal balance.
• A teammate consumed the shared pool.
• A long agent run spent more than expected.
• The panel is showing a cached value.
• You are looking at a different environment or organization.

Workspace balances make cost attribution harder, not easier. The bill is shared, so the useful question shifts from who spent it to what kind of work spent it.

Monitor the right pool

1. Confirm which account the tool is using.
2. Record the starting balance before a heavy task.
3. Connect Amp in UsageAtlas with the same account.
4. Set an alert at the level where work would need to stop.
5. Review History weekly for the burn rate.

For the compute side of the same charge, see Amp Orb hours. For setup, see how to track Amp usage.

Workspace spend needs a habit

When the balance is shared, nobody feels the cost of a long run until the pool is empty. A weekly review of the workspace balance, plus a note of which task ran long, is enough to keep it predictable.

1. Record the workspace balance every Monday.
2. Note the largest task of the week.
3. Compare the drop with what that task produced.
4. Move routine work to a cheaper mode if the ratio is poor.

For the compute measure behind the charge, see Orb hours.

Questions, answered