Run Balance
Run Balance is the execution quota consumed whenever your organization builds, tests, or executes AI agents, functions, and workflows. Your central Wallet holds standard withdrawable cash reserves; Run Balance is the active compute fuel powering execution across the platform.
The two balance buckets
Section titled “The two balance buckets”Run Balance is managed across two distinct buckets, each operating under its own lifecycle rules.
| Bucket | Primary source | Expiration | Usage priority |
|---|---|---|---|
| Expirable balance | Monthly enterprise plan allotments and promotional credits | Expires automatically at the end of each billing cycle or promotion window | Deducted first |
| Non-expirable balance | Direct card purchases, manual top-ups, and transfers from Wallet funds | Persists indefinitely across plan upgrades, downgrades, and billing cycles | Deducted second, once expirable balance is exhausted |
Consumption and execution costing
Section titled “Consumption and execution costing”Every tool invocation, agent query, or multi-step workflow run deducts from your organization’s active Run Balance.
- Transparent calculation — The total cost per execution combines the underlying foundation model compute cost with any custom creator-set fee.
- Audit transparency — The central Transactions Log records every individual run charge in real time, capturing the status, execution timestamp, deduction bucket, and associated agent ID.
Topping up and managing funds
Section titled “Topping up and managing funds”Administrators can replenish execution quota three ways.
- Direct card purchase — Purchase non-expirable quota using a corporate credit card or ACH payment.
- Wallet transfer — Deposit funds into your central enterprise Wallet for long-term hold, then transfer into Run Balance as needed.
- Plan upgrades — Upgrade your organization’s monthly subscription tier to increase the baseline monthly expirable allotment.
When the balance runs dry
Section titled “When the balance runs dry”When an organization’s Run Balance reaches zero:
- Execution pauses — Attempting to execute a tool, query an agent, or trigger a workflow returns a
402 Payment Requiredstatus and halts execution. - Data stays intact — All agents, custom code functions, workflow structures, connectors, and system data remain completely intact. No assets are deleted or altered.
- Resolution is instant — Topping up non-expirable quota or transferring funds from the Wallet immediately restores execution across the entire organization.
Governing balance at enterprise scale
Section titled “Governing balance at enterprise scale”At enterprise scale, Run Balance is managed centrally by IT administrators to prevent unexpected workflow stalls.
- Centralized allocation — A single pool of execution compute is shared safely across all teams and departments under administrative oversight.
- Threshold alerts — Administrators configure automated budget alerts, for example a notification when the non-expirable balance drops below 15%, so quota is topped up before critical production workflows stall.
- Departmental mapping — Pair Run Balance tracking with departmental budgets to correlate compute consumption with business value across teams.
Limits, per-team budgets, and alerting are configured on their own page — see the Cost Optimization Center for the full detail.
A quick example: proactive quota management
Section titled “A quick example: proactive quota management”Consider an enterprise administrator managing a high-volume customer support automation.
- Consumption alert — The admin receives an automated alert that Run Balance is drawing down faster than usual because of a new ticket-triage workflow.
- Analytics review — The admin opens adoption and usage analytics, verifies the workflow is successfully handling 80% of incoming support tickets, and confirms the return.
- Proactive top-up — The admin transfers funds from the enterprise Wallet into the non-expirable bucket and sets an automated replenishment threshold, so support operations run without interruption.
Run Balance vs. Wallet
Section titled “Run Balance vs. Wallet”| Dimension | Enterprise Wallet | Run Balance |
|---|---|---|
| Primary purpose | Holds cash reserves and financial deposits | Powers tool, agent, and workflow execution |
| Usability | Withdrawable or transferrable | Non-withdrawable compute fuel |
| Expiration rules | Never expires | Expirable from plan allotments, non-expirable from top-ups |
| System behavior | Passive balance reserve | Deducted automatically per API or workflow run |
Next steps
Section titled “Next steps” Cost Optimization Center Set departmental spend limits, budgets, and threshold alerts.
Adoption and usage analytics Analyze platform consumption trends and where compute is going.
Capability matrix Review which roles can purchase, transfer, and allocate balance.