Reference
Billing and usage
Mobius bills your organization for the AI usage and platform work it does. Open Organization > Billing to see your plan, your remaining credits, what's been charged recently, and your invoices.
Owners and Admins can change plans, buy credits, open the billing portal, and set organization-wide limits. Everyone else sees the same numbers without the controls.
Reading the page
Three views:
| View | Answers |
|---|---|
| Overview | What plan am I on, how many credits are left, is anything wrong? |
| Usage | What's actually spending the credits? |
| Settings | What plan and what limits should we have? |
Available credits is what Mobius can spend right now, and it comes from two places:
- Included with your plan, which resets each billing period and is spent first.
- Your credit wallet, which holds credits you bought or were granted. It's spent after the included ones and carries over until used.
The top navigation and the Overview card show the total. The Credits card breaks it into both sources. This trips people up: a wallet at zero doesn't mean you're out of credits, if this period's included credits are still there.
Where did the credits go?
Open Usage and start with Recent credit charges. Each row names what was used, which AI model where relevant, how much, and what it cost. Follow the row through to the run behind it.
Credit movements is the wallet ledger. Purchases and grants add to it. Metered work draws down your included credits first, so the ledger only records the part that spilled into the wallet. Work that cost nothing still shows up in the usage table, so you can tell "we did this and it was free" apart from "we didn't do this".
If you bill clients for this work, one organization per client is what makes the usage breakdown line up with an invoice.
Stopping runaway spend
Owners and Admins can set Max steps per run under Settings. It's an organization-wide ceiling, not a target. Individual jobs can set something lower; none can go above it.
Keep it conservative for jobs that call outside systems or expensive models, and raise it only when something real needs more.
This is the blunt instrument. The precise ones, per-job spending caps and time limits, are in guardrails, and you should set those on every unattended job.
After a payment or plan change
Mobius may show the operation as processing for a moment while the payment provider confirms. Leave the billing page open; it checks and refreshes the subscription, credits, usage, and invoices once things settle.
If you come back from checkout without paying, Mobius cancels the pending operation where it can. If your payment went through at the same moment, it finishes reconciling rather than falsely telling you it was cancelled.
Next
- Cap spend with guardrails.
- Trace charges back to the conversation in agent sessions.
- Limit what agents can reach with tools and skills.
- Split usage by client with separate organizations.