Skip to content
Download MarkdownBack to AethisJoin the waitlist

Manage spend and usage

Aethis separates Agent budget tracking from the workspace’s enforced monetary control:

  • The workspace Monthly spend cap is the enforced ceiling for supported cost-bearing execution.
  • An Agent’s Usage & limits shows its Monthly spend cap, Spend this month and Alert at warning threshold so you can understand which workloads contribute to workspace spend.
  • Your plan’s governed-action allowance is a separate count. A blocked or held action can still count because Aethis evaluated and recorded it.

Before you begin

Section titled “Before you begin”

You need permission to change workspace settings and a monthly amount approved by the workspace owner. Agree on who responds to a Budget Enforcement alert and what work may be paused when the cap is reached.

Choose a workspace cap that reflects the total supported cost-bearing traffic in the workspace. For example, a Production workspace with a USD 2,000 operating limit should use that workspace total. Agent caps can divide the monitoring target among workloads, but the workspace cap remains the documented execution boundary.

Set Agent tracking and alerts

Section titled “Set Agent tracking and alerts”
  1. Open the Agent and find Usage & limits on Overview.
  2. Set the Monthly spend cap used to track this workload.
  3. Set Alert at to the percentage where its owner should investigate, then save the change.
  4. Confirm that Spend this month appears against the saved cap.

Expected result: the Agent shows current spend against its cap and can warn at the selected percentage. Alert at does not stop execution, and the Agent cap should not be treated as an independently enforced boundary.

Set the workspace cap

Section titled “Set the workspace cap”
  1. Select the workspace you want to control.
  2. Open Settings > Workspace.
  3. Find Workspace spend controls.
  4. Enter the Monthly spend cap and save the change.
  5. Confirm that the saved cap and Current spend appear for the same workspace.

Expected result: the workspace cap becomes the hard monetary boundary. When current spend reaches it, Aethis stops the next supported cost-bearing execution before it runs.

Find what is driving spend

Section titled “Find what is driving spend”

Open Agents and start with the workspace totals. Then open an Agent’s Overview and compare:

Measure Use it for
Monthly spend cap The Agent’s tracking target. Do not treat it as the documented execution stop.
Spend this month Compare the Agent’s attributed spend with its cap and with other Agents in the workspace.
Alert at Decide when the Agent owner should investigate. This threshold does not stop execution.
Workspace Current spend Compare aggregate spend with the workspace’s enforced Monthly spend cap.

Use View Activity from the Agent to inspect the time window around a spend increase. Filter to the Agent and relevant Connection, then compare the Action Records with the workload’s expected traffic.

Respond near or at the cap

Section titled “Respond near or at the cap”
  1. Open the Budget Enforcement alert and select Assign to me.
  2. Check the affected workspace, current spend, cap and related Agents.
  3. Use Agent usage and Activity to distinguish expected volume from a retry loop, an unexpected model route or another anomaly.
  4. If traffic is unsafe, pause the affected Agent route. If traffic is expected, have the workspace owner decide whether to change the cap or defer work.
  5. Resolve the alert only after the underlying spend condition or traffic cause is addressed.

Do not retry a cost-bearing action solely because it was stopped at a budget boundary. Confirm the action’s outcome and the upstream state first, especially when an Action Record says Outcome unknown.

Diagnose discrepancies

Section titled “Diagnose discrepancies”

The Agent has spend, but the workspace total looks wrong. Confirm that both views use the same workspace and monthly period. Then clear Activity filters and compare the relevant Agents and Connections for that period.

The Agent spend appears stale or empty. Confirm the selected workspace and monthly period, then check that the Agent’s governed traffic appears in Activity. If records are present but spend is still unavailable, preserve the Agent and Record IDs for support.

Calls stop before the cap appears reached. Check the Agent’s status and Connection state. Paused, Suspended, Disabled, Frozen and Unavailable describe different controls and failures; see Statuses.

Spend reached the cap, but you need to know what ran. The cap affects the next supported cost-bearing execution. Use Investigate in Activity to distinguish completed, blocked, failed and unknown outcomes.

Section titled “Related controls”