Skip to main content
Studio separates operational usage from billing administration. Usage explains where AI, calls, and transcription consumption came from. Billing manages the organization’s plan, payer information, payment methods, tax IDs, and invoices. The status bar can show the remaining allowance or top-up balance while you work. Open the usage control for the detailed Usage view; use the display preference if you do not want the balance pinned persistently.

​
Usage view

Per-chat detail is intentionally self-only. Organization aggregate or member summaries do not grant an admin access to another person’s chat content.

​
Understand AI cost

Studio records input, output, cache, model, and billed usage for AI work. In the model table, use filters to narrow the date, surface, or member and inspect the records behind a total. The conversation cost view shows the models used in that conversation and a cost breakdown when pricing is available. Auto can route individual turns to different models, so one conversation can contain more than one model. Cost is most affected by:
  • Model and context-window choice.
  • Large attachments, tool results, and long un-compacted history.
  • Browser AI Grounding and image-heavy work.
  • Agentic turn count and sub-agent work.
  • Repeated polling or retries against an unavailable source.
Use /compact with optional focus instructions when a long chat still matters but most history no longer needs to remain verbatim.

​
Allowance, top-ups, and windows

Your plan provides an allowance over a defined usage window. The UI shows percentage remaining instead of exposing implementation-level raw credits. Purchased top-up balance is shown separately in currency and can cover additional eligible usage. Top-up balance carries across plan changes and expires 12 months after purchase. The top-up review shows the exact charge and saved card before payment.
When a rolling allowance window is full, a top-up may let work continue immediately. Otherwise, wait for the window reset or ask an administrator to review the limit.

​
Top up safely

1

Open the top-up flow

Use the persistent balance or a usage-limit prompt. Only an authorized billing owner can complete organization billing writes.
2

Choose the amount

Select a preset or enter the supported amount in currency.
3

Review the charge

Confirm the amount, organization, saved payment method, and top-up expiry statement.
4

Complete payment

Some cards require Strong Customer Authentication in a Stripe-hosted flow. Return to Studio after the payment completes.
5

Verify the result

Confirm the balance updates and open Billing → Invoices for the hosted invoice or PDF receipt.
Do not retry repeatedly when payment status is unclear. Refresh invoices and balance first so an in-flight authorization does not become an accidental duplicate attempt.

​
Usage limits

Authorized administrators can set soft or hard limits for supported metrics at organization scope and, where supported, user scope.
  • A soft limit warns while allowing continued use.
  • A hard limit blocks covered usage when the threshold is reached.
Limits can cover AI spend or tokens, call minutes, transcription seconds, and transcription sessions. Treat a limit as a guardrail, not an accounting report: check the Usage and Billing views for the financial picture.

​
Billing pages

Plan downgrades take effect at the end of the billing cycle when Studio shows them as scheduled. Confirm the effective date in the Plan view before assuming access or allowance has changed.

​
Billing ownership

Billing writes are restricted to the organization’s responsible billing owner. Transfer billing ownership before that person leaves the organization. A normal organization admin may be able to inspect usage without being authorized to change the plan or payment method.

​
Troubleshooting

Settings

Set the default model, context window, turn limit, and follow-up behavior.

AI Copilot

Understand models, context, compaction, turns, and Browser AI Grounding.