Credits, budgets and usage¶
HiveAI uses prepaid workspace credit for chargeable work. Budgets limit how much a user, team or department can commit within a UTC calendar month. These controls help administrators manage spending while giving users a clear view of why work can proceed or is blocked.
A budget is a spending limit; it does not add credit to the workspace. Buying credit does not remove an applicable budget limit, grant permission to use protected information or enable an unavailable capability.
Availability¶
The backend implements credit funding, reservation, settlement, release, expiry, budget policies and reconciliation. Current Final Screens places AI credits and budgets in Tenant Admin and shows personal-budget creation, editing, removal and read-only states. The inspected frontend does not yet implement these credit and budget screens. Follow the guide as the intended experience where your environment provides it.
The design also distinguishes no funded account, exhausted credit and an unavailable balance. These are different outcomes. A failed read does not mean the workspace has no money or no configured budget.
Budget changes have an unresolved backend processing constraint. The designed save and removal steps are not evidence of a working deployed journey; confirm the current saved policy before relying on a new limit.
Understand the amounts¶
| Amount | Meaning |
|---|---|
| Available workspace credit | Credit that remains available after recorded charges, active holds and expiry, including applicable platform-funded adjustments |
| Added credit | Funding recorded for the workspace; the amount is not a cash balance or a monthly allowance |
| Held credit | Credit reserved for work or a refund process that has not completed |
| Used credit | Charges that have been settled; this can include conservatively resolved work whose answer could not be recovered |
| Expired credit | Unused credit that has passed its expiry |
| Monthly budget remaining | The policy limit minus usage settled and credit held in that scope's UTC month, with a minimum displayed remainder of zero |
Amounts use microcredits, the platform's accounting unit. Do not read a microcredit figure as a currency amount. Purchase prices and checkout currency come from the current commercial offer.
A request can appear in a user's, team's and department's budget at the same time. Those are overlapping controls on the same work. Adding their usage together would count that work more than once.
How paid work affects the balance¶
Before chargeable work begins, the system attempts to reserve credit. An applicable hard budget limit or insufficient spendable credit can prevent the reservation. When measured usage settles successfully, its charge is retained and the unused portion of the reservation is released.
Some work has an uncertain outcome. A timeout or missing answer does not prove that the provider did no work. Protected reservations remain held while that outcome is reconciled. For eligible unknown provider outcomes, recovery can charge the full reserved amount without repeating generation. The guide explains how to investigate safely.
An estimate, an approved limit, a reservation and a final charge answer different questions. A question estimate is nonbinding. A displayed cost for one part of a conversation is not automatically the total cost of the whole request.
Monthly budgets¶
Budgets can apply to a user, team or department, subject to current policy and entitlement. A department budget requires Advanced entitlement. The summary follows the current user's resolved scopes; it is not a directory of every budget in the organization.
A policy has a required positive hard limit, optional warning thresholds, an effective start time and an enabled setting. Warning thresholds inform the reader; they do not stop work by themselves. A new reservation is denied when held credit plus settled usage plus the requested reservation would exceed an applicable hard limit.
Updating or removing a policy preserves existing recorded costs and reservations. Disabling a policy or setting a future start time stops that policy from governing new reservations until it applies again. Other budgets, credit availability, licensing and permissions continue to matter.
Current coverage limitation¶
Team and department limits have a separate implementation gap. If the system cannot establish a person's current organizational membership, some requests can proceed without those limits being included. Very large sets of memberships can also be incomplete. A successful request or a short budget summary is therefore not proof that every expected organizational limit was checked.
The integration gap must be resolved and verified in the connected release before those limits can be relied on consistently. Administrators should reconcile expected memberships and existing budget and usage records with support. Changing an allowance does not repair a failed membership check; keep this limitation separate from whether a policy was saved or the workspace has credit.
Funding, expiry and corrections¶
Tenant administrators can start a supported prepaid-pack purchase through Billing. The current purchase model includes packs of 1,000,000 and 5,000,000 microcredits, with credit expiry 12 months after the verified payment's effective time. Availability and the actual price depend on the current plan or commercial contract.
A checkout request or payment screen does not establish that credit is available. Verified payment, the credit grant and the usage balance must be reconciled. Check the existing purchase before initiating another one if a result is delayed.
Unused purchased credit can be subject to a governed refund process. A platform-defect adjustment is a separate, evidence-based credit correction for an eligible resolved charge. Neither is a promise of an automatic cash refund whenever an answer is missing.
For business planning¶
Review available credit, active reservations and applicable monthly limits together. Keep dates and units visible when discussing consumption. A current balance is not a historical monthly spending report, and credit consumption does not by itself measure productivity, return on investment or answer quality.
Continue with managing credits and budgets, conversation costs and recovery, organization-intelligence interpretation and Billing.