Billing and usage

Mobius bills your organization for the AI usage and platform work it does. In a direct-billed organization, open Settings > Billing to see the plan, remaining credits, and invoices, and Settings > Usage to see the shared pool, per-person limits, and what the credits were spent on. A managed organization has only Settings > Usage, because its service provider owns the payment relationship.

The organization owner can change plans, buy credits, open the billing portal, and edit usage limits. Other roles with billing read access see the figures without those controls; an organization Admin does not receive billing mutation authority merely from the Admin role.

What is a credit?

Credits pay for the AI models that do your work and for the paid services they use along the way, like web searches, data lookups, page scraping, and image generation. As a rule of thumb, 100 credits is roughly $1.

Ask an assistant a quick question and it uses a few credits. Ask it to research a topic across a dozen web pages with a more capable model and it uses many more. Routine runs use credits the same way conversations do.

The exact price of a credit depends on how your organization is billed: your plan, your agreement with Mobius, or the service provider that manages your organization. The amounts on these pages are in credits either way, so they compare across people and months.

To judge your own month, open Settings > Your usage. It shows what a typical conversation of yours uses, what your organization's plan includes per person each month, and where your pace is heading.

Reading the pages

Three places:

Where	Answers
Billing > Overview	What plan am I on, how many credits are left, is anything wrong?
Billing > Plans	What plan should we have, and what have we paid?
Usage	Who is using Mobius, what's spending the credits, and what limits apply?

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 billing period is the calendar month, from midnight UTC on the 1st to midnight UTC on the next 1st. An organization that starts mid-month gets a short first period that runs to the next 1st: it's charged for the days it actually has, and its included credits are sized for those days, rounded up to whole weeks. Every period after that is a whole month.

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 > Charges. It covers the current billing month. Usage drivers totals the charges by what was metered, such as model tokens, web searches, and tool calls, and exports as CSV. Models totals them by AI model. Mobius does not list individual charges, in a managed organization or a direct-billed one. To see the token usage of one conversation, open it in agent sessions.

In a direct-billed organization, Credit movements on Billing 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.

Put limits at the right boundary

Open Settings > Usage > Limits to see the current billing period and each person's credits used, effective monthly cap, and whether that cap comes from an individual override or the organization default. Organization Owners and Admins can change caps in direct-billed, contracted, and managed organizations.

Set a Monthly credit cap as the organization default, then override it for specific members when needed. New members use the default automatically. Clear an override to Use organization default. A blank default means no person cap; it does not make the organization's shared pool unlimited. Zero stops new work that consumes credits. Changing a cap does not erase the person's usage for the current billing period. The dates on the page show when that usage resets.

At 80% of a person's cap, their conversation shows a warning with remaining credits and a link to Your usage. At the cap, new platform-funded work stops with the reset date and an instruction to ask an administrator of the organization to raise it. An Owner or Admin sees a link to Usage > Limits instead, where they can raise the cap. Work already admitted can finish and settle above the cap, including concurrent conversations. A cap is a check before new work, not a reservation that guarantees the final total stays below it.

A shared assistant's use counts against the person who starts the work, not the assistant's owner. Individual routines count against their owner. Team routines use the organization pool, not the responsible person's cap. Machine work with no identified person also uses the organization pool. Each person can inspect their own credits under Settings > Your usage.

For a direct-billed organization, the owner can also choose what platform-funded work does when the shared pool and wallet are empty: stop, or use the configured economy model. In a managed organization, the service provider controls that pool-exhaustion policy while the organization's Owners and Admins can change person caps.

Those period controls answer who may consume the organization's credits. Put the narrower boundary on the work too: each routine has Credits per run and Credits per 24 hours, and each assistant turn has an active-work timeout. Review those guardrails before scheduled or event-triggered work goes live.

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.