Credits and usage

Understand what a Credit balance accomplishes, read your workspace usage, and earn or top up Credits.

Credits are Runner’s universal usage unit. Eligible LLM, image, video, automation, workflow, simulation, skill-driven, and deployment operations all deduct from one displayed balance.

What this covers

Estimating what a balance accomplishes, selecting one reporting range and reading every block against it, earning bonus Credits, and understanding how usage is recorded.

Availability and prerequisites

Usage is scoped to the current workspace, not one store.
Data can be empty when the workspace has not used Credits in the selected range.
Credit grants, expiration, and purchase eligibility depend on the grant or plan shown in your account.
Use Usage & Credits for your balance and recorded spend; use the current purchase confirmation for prices.

Entry path

Open the intended workspace, then select Settings → Usage & Credits. Confirm the workspace name in the settings sidebar.

English annotations: Usage and Credits entry in workspace Settings

English callouts highlight the controls. Select the image to enlarge it.

Open Usage & Credits under the intended workspace. This image shows the entry, not a balance or recorded usage; inspect those values in your own workspace.

Use your own recent tasks to estimate the next similar change. Start with a small, well-defined request, then check its recorded Credits in Workspace activity. Model choice, context size, output length, media, retries, and task complexity all change the total; there is no fixed price per message or guaranteed number of store builds per balance.

Estimate your next store build

Open Settings → Usage & Credits in the workspace where you will build.
Make one small, representative request, then find its recorded spend in Workspace activity.
Compare recent tasks of similar scope and model choice. Estimate initial generation and later revisions separately.
Add the work you expect to repeat, and allow for media generation, retries, and larger changes. Check recorded spend again after each stage.

For example, if your own activity records 200 Credits for generation and 20 Credits for each of three similar revisions, those tasks total 260 Credits. These numbers illustrate the calculation; they are not typical costs, a benchmark, or a quote for your next store.

Check: Your estimate comes from comparable recorded tasks. A Credit balance does not guarantee a fixed number of stores or revisions.

For the monthly allowance included with each plan, see Subscription plans.

Controls and reports

Entry or button	Why it is useful	What happens next
7 days	Inspect recent activity.	Every chart, summary, category, and activity block updates to seven days.
This cycle	Review the current billing-cycle window.	The page uses the elapsed current cycle shown for the workspace.
90 days	Look for a longer trend.	Every usage block updates to the longer range.
Credits left card	See remaining and total Credits for the current plan/grants.	The progress bar and displayed refresh date explain the current balance state.
Upgrade	Compare plans when more included capacity is needed.	Runner opens Plan & Billing.
Buy Credits	Review an eligible extra-Credit purchase.	Runner opens Plan & Billing; no purchase occurs until its confirmation is completed.
Credits per day	Find busy or quiet dates.	Hovering a bar shows that date’s usage.
Where your Credits came from	Understand plan, daily, signup, purchased, and other grants that apply.	Each row shows source, cadence, note, and Credits.
Where your Credits went	Compare spend categories and run counts.	Bars show each category’s share for the selected range.
Workspace activity	Inspect recent tasks behind the spend.	Category tabs filter the same Task, Project, Type, Credits, and Time columns.

Review usage

Open Workspace → Usage & Credits.
Select 7 days, This cycle, or 90 days.
Read Credits left before interpreting spend.
Compare Used in range, Daily average, and Busiest day.
Use Credits per day to find when usage changed.
Compare sources with spend categories.
Filter Workspace activity to identify the tasks involved.
If you need more capacity, open Upgrade or Buy Credits, then review the separate billing confirmation.

Earn bonus Credits

Open the check-in or quest shown in your account and read the reward before claiming it. After a successful claim, return to Usage & Credits and inspect the source and balance.

Daily check-ins, consecutive-day bonuses, and introductory quests have separate eligibility and limits. Read the current cap and expiry attached to each grant; a monthly earning cap and a maximum stored bonus balance are different limits. Do not treat bonus Credits as an indefinite rollover balance.

How usage is recorded

Usage is recorded after an operation completes and can take a short time to appear.
One request can produce several records when Runner uses multiple models, tools, media operations, simulations, or deployments.
If a total looks unexpected, compare the timestamp, project, action type, model or provider, and any retries before contacting support.

Understand the numbers

Remaining balance and selected-range spend answer different questions; they do not need to be equal.
The Credits-per-day chart reports daily spend, while the source card reports grants and remaining balance.
A category can show runs with zero Credit spend.
Activity rows show recent tasks for scanning, not a complete permanent audit log.
Dates use the timezone on your current device.

Common questions

Question	Answer
Why did two similar prompts use different amounts?	They may have used different context sizes, output lengths, tools, models, agent steps, retries, fallbacks, media, simulations, or deployments.
Does sending a message consume a fixed number of Credits?	No. Credits follow the metered operations actually performed for the request.
Do manual edits consume Credits?	Editing content or code yourself creates no model usage. Asking Runner to make or explain the edit can.
Are failed requests always free?	Not necessarily. A failure with no provider-reported usage has no model cost, but usage reported before a failure, or during another successful attempt, can still be recorded.
Is a skill charged separately?	No. Activating a skill adds no flat fee; the operations it performs deduct from the same balance.
Do bonus Credits roll over?	Read the expiry on each grant. Check-in earning limits, stored-balance limits, and streak bonuses can follow different rules.
How does the seventh check-in bonus work?	Each eligible daily check-in awards 10 Credits, and every seventh consecutive claim adds a streak bonus. The claim screen shows the current amount before you collect it.
Is a Boost Pack a subscription?	No. It is a one-time purchase of 350 Credits for US$9.90.

States and limits

Out of Credits highlights a zero remaining balance and keeps billing actions available.
Empty activity says there are no logs for the current filter or range.
A source can show zero when it is actionable but not yet claimed.
Passive grant types appear only when they contributed Credits.
Loading covers both balance and consumption data; wait for all cards before comparing them.

Troubleshooting

If two numbers seem inconsistent, confirm every block is using the same selected range.
If a task is missing, clear the activity category filter and try a longer range.
If the balance did not change after a purchase, return to Plan & Billing and confirm that the purchase reached a completed state before refreshing.
If no usage appears, verify that you opened the workspace where the task ran.
If you need a charge or plan decision, use Plan & Billing rather than an old usage screenshot.
For an unexpected charge or a data-processing requirement, contact team@adaptivemachines.ai with the workspace, project, approximate timestamp, and usage event details.