Check your allowance
Open your organization’s billing view, or use the CLI:How runs use credits
Gauge reserves credits when creating runs. For runs using Gauge’s provider keys, the final credit charge is reconciled with the run’s metered AI usage after successful execution. The balance while runs are in progress can therefore differ from the balance after they settle. A run that fails or times out receives a run-credit refund. A successfully executed session can still fail an eval criterion; that is a measured outcome, not an execution failure. If you stop a session, the charge depends on when it stopped. A run stopped while still queued costs 0 credits. For runs using Gauge’s provider keys, a run stopped while the agent is working is charged a base fee plus the AI usage measured until it stopped. Gauge releases the rest of its reservation. Stopped runs do not receive the failure refund. With BYOK, the provider charges your provider account separately and Gauge applies its run credit charge. Confirm which funding arrangement you are using before interpreting costs.If a run cannot start
Check the available balance, subscription state, and Can run indicators ingauge billing status. A run needs sufficient available credits for its reservation; a small positive balance may not be enough. A multi-run request can produce fewer runs than requested when credits are limited, so check the returned run count.
Resolve an unpaid or expired subscription, wait for renewal, or change the plan through billing as appropriate. Provider-key errors need a provider connection fix, even if credits are available.