Usage & the activity ledger
Settings → Usage is the accounting page for your account: your balance, your plan, and a line-by-line ledger of everything that earned or spent credits.
The credits bar
The bar at the top shows credits remaining against your monthly budget, with the reset date for the current billing period (subscribers reset on their billing date; Free accounts follow the calendar month). Below it sit the Top up field and your subscription controls.
Remember the two pools: monthly credits reset on that date, purchased credits don't. The split is explained in How credits work.
The spend chart
Above the ledger, a bar per day shows the last 30 days of spend, split into the four categories that cover everything: Generations, Agents & chat (copilot conversations, Build agent work, and scheduled agent runs), Compute (sandbox machine time), and Other. The legend carries each category's 30-day total, and hovering any bar segment names the day, the category, and the exact credits.
Reading the ledger
Entries are listed newest first. Most are one credit movement; Build sessions and agent runs roll all of their small charges into a single line for the outcome they paid for:
| Entry kind | What it means |
|---|---|
| Monthly credits | Your plan budget arriving at the start of a period. |
| Top-up | Purchased credits from a Stripe checkout. |
| Generation | An image, video, audio, or upscale job — with the model and duration/count. |
| Agent | An editing-agent or copilot conversation, metered by tokens. |
| Build session | One conversation with the Build agent — see below. |
| Agent run | One run of a scheduled or triggered agent, tokens and machine time combined. |
| Transcription | Automatic captions/transcripts, at 72 credits per hour of audio. |
| Storage | Historical overage charges from before storage became a hard quota (storage no longer costs credits). |
| Adjustment | Everything else: your 50 signup credits, the first-top-up bonus, support credits, and period-rollover settlements. |
Generation entries are clickable — the preview opens the asset that was created, with its prompt and model, so you can always answer "what was that 30 credits for?" Build session and agent run entries open the app or run they paid for.
What a Build session costs
A Build session row aggregates two meters, and the row says which is which ("42 agent turns · 2 compute"):
- Agent turns are the AI model calls that did the work. This is almost always the bulk of a session's cost. Each model's rate per million tokens is shown in the composer's model picker before you pick it, and a session is billed on its exact total — never rounded up call by call.
- Compute is the sandbox machine's awake time, at roughly 8 credits per hour. The sandbox parks itself after 8 idle minutes and costs nothing while parked; opening the workspace wakes it. Compute is priced to be a rounding error next to the agent's work — a full day of active building is typically under 20 credits of compute.
A session's row shows the date range its charges span. A session you ran on Monday whose sandbox parked after midnight reads "Mon – Tue", not as new Tuesday spend.
Scheduled agents bill as their own Agent run rows — one line per run, so an automation's cost is always visible as exactly that.
Shared projects
Work billed to a shared project appears in the project owner's ledger, with attribution for the contributor who ran it. If you're seeing entries you don't recognize, check whether you own a busy project — details in Pooled billing.