Usage
Review compute and AI allowances, inspect session charges, and control automatic credit spending.
Open your personal usage
- Open qBraid Account.
- Select qBraid Default in the workspace switcher to inspect your personal usage.
- Open Account > Usage in the sidebar.
- Select Overview for balances and allowances, or Session History to investigate individual compute sessions.
The same page shows your usage within an organization when that workspace is selected. It does not show every member’s consumption. Administrators can use Organization usage for that view.
Overview
Start with the cards near the top of Overview:
| Card | What to check |
|---|---|
| Available Credits | Your qBraid wallet balance in the selected workspace. |
| Compute Hours | Subscription compute allowance consumed, total quota, and renewal countdown. |
| Storage | Stored data in GB and the displayed storage quota. |
| Credits Charged | Recorded compute credit charges for the selected history range. |
The Understanding Your Usage card separates subscription compute from on-demand billing. Open the question-mark help controls beside individual metrics for their definitions.
How compute hours and charges work
Subscription CPU Lab instances use your compute-hours allowance first. Compute hours are vCPU-hours, calculated as session duration multiplied by the number of vCPUs. One hour on a 2-vCPU instance consumes two compute hours.
Compute Time, session Duration, and Total Compute Time measure elapsed running time. They do not multiply duration by machine size. The Compute Hours quota also follows its renewal date, while historical totals follow the selected date range. These numbers can therefore differ without indicating a billing error.
On-demand instances use wallet credits instead of subscription compute hours. They charge for compute while running and can charge for retained storage while stopped. Terminating an on-demand instance stops its storage charges but deletes its disk. Download needed files first. See On-demand instances.
Change the history range
- Scroll to Daily Usage.
- Open its range selector.
- Choose 7 days, 14 days, 30 days, 90 days, 1 year, or All time.
- Compare the chart, session breakdown, Credits Charged, and Summary for that range.
The default range is 30 days. It changes the historical totals, not the wallet balance or monthly allowance.
The chart shows Subscription Hours, On-Demand Hours, and Credits Charged. Read hours on the left axis and credits on the right. Hover over a point for its daily values.
The Subscription Sessions and On-Demand Sessions cards show session counts and running time. The on-demand card also separates Compute Credits from Storage Credits. Summary shows total running time, the subscription and on-demand session counts, and total credits charged.
A pending-settlement notice means recorded charges can still update. If on-demand usage is temporarily unavailable, the displayed totals may be incomplete. Refresh after the service recovers before treating them as final.
Turn on automatic credits for compute
Enable this setting if you want subscription CPU sessions to use wallet credits after the compute-hours allowance runs out. Check Available Credits first. Enabling the setting does not purchase credits.
- Open Account > Usage > Overview in the intended workspace.
- Find Compute Settings.
- Turn on Auto-switch to Credits.
- Wait for Auto-switch to credits enabled.
- Review your wallet balance and session charges as you continue using compute.
Changes save when you toggle the switch; there is no separate Save button. The switch is unavailable while the update runs. If Failed to update settings appears, the update failed and the switch returns to its previous setting. Retry and check the success message.
To turn automatic credit spending off, use the same switch and wait for Auto-switch to credits disabled. With fallback disabled, subscription CPU sessions are terminated when compute hours run out, and new subscription launches are blocked until the allowance renews or fallback is enabled. Save your work before exhausting the allowance.
This setting applies to subscription CPU fallback. On-demand instances already use credits, and AI has its own setting below. See Lab usage limits for allowances.
Session history
Use this tab to identify a long-running session, compare subscription and on-demand work, or investigate a charge.
- Open Session History.
- Select All, Subscription, or On-Demand to filter by billing tier.
- Use All Status to select a status, such as Running, Stopped, Completed, or Error.
- Read the matching rows, then use Previous and Next for additional pages.
- Select a row to open its billing details. Keyboard users can focus a row and press Enter or Space.
The table shows 10 sessions per page. Changing a filter returns to page one. These filters are separate from the Overview chart’s date range.
| Column | Meaning |
|---|---|
| Start and End | Recorded session times. An unfinished row can show Running… instead of an end time. Check its Status too. |
| Tier | Subscription or On-Demand billing. |
| Profile | The compute profile or instance label, with supporting vCPU or instance information. |
| Duration | Elapsed running time, rather than vCPU-hours. |
| Credits | Recorded credit charges. A dash means no positive charge is shown. |
| Status | The recorded session state. |
An Unpaid charges indicator means usage could not be covered by the available credits. Settlement pending means billing is still processing. These indicators describe different conditions.
Inspect a session’s billing details
In this example:
- On-Demand identifies wallet-credit billing. Terminated is the recorded instance status.
- Charged: 0.17 Cr is the recorded charge for the session. The Compute line and bottom Total also show 0.17 credits.
- Ran for: 3m 38s is the elapsed runtime. The two event windows, 3m 9s and 29s, account for that runtime.
- Events: 2 counts the recorded billing events. It does not mean two separate final wallet charges.
- PREPAID · PER-MIN describes the compute billing model. The expanded rows show recorded event times, types, windows, and credit values.
The event rows show 1.14 and 0.17 credits, but adding them does not give the final session charge. On-demand compute is charged in advance, with unused time refunded. Use Charged, the compute/storage line items, and Total to read the recorded charge. This screenshot alone does not show the full refund or settlement history needed to reconstruct each event’s credit value.
The dialog identifies the session and shows Charged and Ran for. Subscription sessions also show Compute, the vCPU-time drawn from the allowance. On-demand sessions show Events and a compute/storage breakdown when available.
Read Billing events for the recorded usage windows. On-demand sessions provide Show all [number] events and Hide events controls. The detailed events are meter readings; they are not necessarily individual wallet charges. Use the Charged total and compute/storage line items to reconcile charges, rather than summing meter readings yourself.
If the dialog reports that it is showing only the latest events, the displayed timeline is incomplete even though the charge total covers the session. No billing events yet. is different from Couldn’t load billing events. Use Retry for a loading error.
Select Report Issue to open a support request with the session identifier and billing details already supplied. Add what you expected and what looks wrong before submitting.
Outstanding balances
An Outstanding Balance alert appears when there are unpaid compute charges. It can include subscription debt and on-demand debt together. The amount owed is different from the available wallet balance and from charges still awaiting settlement.
Add credits through the Wallet, then wait for settlement before retrying a blocked launch. The alert warns that sessions can be terminated or new sessions blocked while debt remains. If the balance still looks wrong after settlement, inspect the session’s billing details and use Report Issue.
AI chat usage
Scroll to AI Chat Usage in Overview. It shows the monthly quota percentage, Status, Renews, and Can Send.
- Using Quota means usage is drawing from the included allowance.
- Using Credits means usage is drawing from wallet credits.
- Quota Exhausted means the included allowance has run out.
- Can Send reports whether requests can currently proceed.
Turn on automatic credits for AI
- Check that the intended workspace has enough wallet credits.
- Find AI Chat Usage, below the simulator section.
- Turn on that card’s Auto-switch to Credits control.
- Wait for AI chat auto-switch to credits enabled.
To stop automatic AI fallback, turn the same control off and wait for AI chat auto-switch to credits disabled. If Failed to update AI chat settings appears, retry the update. The compute switch does not change this setting.
Review AI usage quotas and AI models for model eligibility, token rates, and allowance limits. An enabled switch alone does not guarantee that every model is available or affordable.
Simulator usage
The Simulator Usage card tracks your daily job allowance for each simulator.
- Choose a device with the Simulator selector.
- Check jobs used today, percentage used, and jobs remaining.
- Use Range to choose 7, 14, 30, or 90 days of simulator history.
Daily limits reset at 00:00 UTC. Plans without a daily cap show Unlimited instead of a metered allowance. The simulator date selector is separate from the compute chart’s selector. Check the device’s displayed limits before submitting more jobs.
Refresh or recover missing data
Use Refresh at the top of Usage to reload the overview, AI allowance, and simulator data. If Error loading usage data or Couldn’t load your sessions appears, select the associated Retry button.
For No sessions found, select All and All Status before concluding that the workspace has no history. Check that you selected the workspace where you ran the sessions. A failed query is not an empty history.
Download your files
You can download Lab files without starting a session from Dashboard > Usage Overview > Download Files. Follow Download Lab files. The exhausted-compute help control can also offer a file download when a new session is blocked.
Thanks for your feedback.