The organization wallet holds the credits used for product execution. Individual developers also pay through a personal organization. Free access, request rates, and concurrency limits are separate from calling balance.
Purchases and subscription credits go to the organization fixed in the order; the paying account identifies the payer. Switching organizations does not change an existing order’s beneficiary.
Check balance and purchase credits
- Sign in to Console, confirm the selected organization, and open Billing.
- Review total balance, current reservations, and available credits: available credits = total balance − current reservations.
- To purchase, an owner or admin selects the target organization on the pricing page and reviews the payment amount, credits, and plan before checkout.
- After returning, inspect the order and wallet transactions to confirm credit delivery to the intended organization.
Purchases and payment methods depend on the environment’s payment configuration. The order defines the cash price and credit quantity; there is no universal cash-to-credit exchange rate. Registration, organization creation, onboarding, and resource preparation do not grant calling balance. Increasing a Gateway budget does not add wallet funds.
The first successful subscription payment and each complete renewal credit the amount fixed in the original order. If confirmation is delayed, inspect the original order before paying again. Regular members can read organization billing but cannot initiate organization purchases.
Subscription access lasts until the end of the paid billing period. A successful renewal extends it to the end confirmed by the paid invoice. Canceling renewal or a failed renewal payment keeps the current paid access until that date; access then expires, without a grace period or an automatic switch to Free. A later successful payment restores access only through its paid period. Repeated payment notices do not shorten an already extended period.
Expiry does not delete resources or clear wallet credits, and buying a credit pack does not renew subscription access. Administrator-assigned plans, individual product grants, and suspensions remain in effect according to their own terms. Work already admitted follows the product’s existing execution and settlement rules.
Reservations are not final charges
A credit reservation holds credits for an execution before its final charge is known. The applicable price and budget determine the reservation. Reserved credits cannot fund another call. Once a trustworthy result is settled, the actual charge is deducted and the unused reservation is released.
Execution costs in Billing distinguish the recorded reservation, current held amount, and posted charge. Check execution and financial status separately: successful work may still await settlement, and a network error does not imply zero cost.
Timeouts, missing usage, or uncertain results may leave funds reserved for reconciliation. Do not repeat work with a new request identifier to try to release a reservation. Retain the original execution or invocation ID and ask an administrator to review its details.
How products are measured
| Product | Main measurement and charges |
|---|---|
| Agents | Model-call tokens. Calls through Gateway have one Gateway model-billing source; Agents does not charge a second time for the same model call. One Agent task may make several model calls. |
| Box | Lite uses command wall-clock duration. Sandbox uses confirmed VM runtime-window duration, including idle time; commands inside the window do not incur a second execution charge. |
| Powers | A platform fee for successful tool calls at the published price. Check any own-provider charges separately. |
| Gateway | Managed routes use token pricing or an explicitly published fixed price per successful request or task submission. BYOK currently has zero Cloud invocation service fees, but the provider can still charge. |
Fixed-price asynchronous media tasks are charged when the provider accepts submission. Later generation failure or cancellation does not automatically refund that fee. See Gateway settlement and recovery for the applicable conditions.
Inspect and export usage
- Open organization Usage and filter by product, project or organization-level resources, and time range.
- Open a record to inspect execution status, native measurements, and recorded Cloud credits. Follow the financial link to inspect settlement.
- Use Export current page when needed. This exports only the successfully loaded page, not the full history.
Project attribution is saved at execution time; moving a resource later does not rewrite historical charges. Time inputs use your browser’s local timezone. A page’s record count or charges are not historical totals.
Not recorded and Pending confirmation are different from a measured 0. Do not add tokens, milliseconds, and tool-call counts together. Cache and reasoning tokens are breakdowns, not additional total tokens. Historical charges retain their original price instead of being recalculated at today’s price.
Refund freezes
Refunds reclaim credits under the original order’s rules. Insufficient available balance can freeze new product execution for that organization. Other organizations remain unaffected, and stored billing records remain readable. Some cancellation, state recovery, and VM pause controls remain available for existing work, subject to other permissions.
If a freeze appears, an owner or admin should inspect the original order, held reservations, and the displayed shortfall-resolution process. Repeating onboarding, creating keys, or preparing resources cannot clear the freeze.