Skip to main content
ModuleX billing fits into four ideas. Your plan gives your organization a monthly credit allowance. Credits meter the usage ModuleX runs for you. When the allowance runs out, a prepaid wallet can cover the difference. And a usage gate checks all of this before each piece of managed work begins. This page gives you the whole picture at a glance. Each part links to a page with the full detail when you need it.

The four parts of billing

Plans

Free, Pro, Max, and Enterprise. Your plan sets your monthly credit allowance and your limits.

Credits

The unit ModuleX bills in. Credits meter managed runs, tool calls, model usage, and knowledge retrieval.

Wallet

A prepaid balance that covers usage beyond your plan allowance, with manual top-ups and auto top-up.

Usage gate

The check that runs before each piece of managed work, so you are never billed for work that could not be admitted.
🎬 MEDIA PLACEHOLDER · MX-MEDIA-1240 · [IMAGE] [IMAGE_DESCRIPTION]: A single diagram showing how a plan, credits, the wallet, and the usage gate fit together for one organization. [IMAGE_DETAILS]: One illustration (not a screenshot), 16:9, light theme, ModuleX brand palette. Draw a left-to-right flow. Start with a box labeled “Plan” feeding a “Monthly credit allowance” meter. Below the meter, a separate box labeled “Wallet (prepaid balance)” with an arrow that joins in only when the allowance is empty. In the center, a gate icon labeled “Usage gate — checks before each managed action”. On the right, three small chips labeled “Run”, “Tool call”, “Knowledge retrieval” that pass through the gate and decrement the meter. Keep wording inside shapes minimal; the goal is to show plan → allowance → (then) wallet, with the gate in front of everything.

How it works in one paragraph

Managed usage is priced in credits, where **1,000 credits cost 1.00(onecreditis1.00** (one credit is 0.001). Each plan gives your organization a monthly credit allowance. As you use ModuleX, that allowance is drawn down. If you are on a paid plan and you turn on overage, work that goes beyond the allowance is paid for from your prepaid wallet. Before any managed run, tool call, model call, or knowledge retrieval starts, the usage gate confirms you have budget — so you are never charged for work that was not admitted.

Credits at a glance

A credit is the single unit ModuleX bills in for managed usage. It maps to money at a fixed rate, so a credit balance is easy to reason about.

1,000 credits = $1.00

Credits convert to dollars at a fixed rate of $0.001 per credit, the same rate for your plan allowance and your wallet.

One run = one credit

A single workflow run or one Assistant turn costs one credit, separate from any model or tool usage inside it.

Usage is metered

Model usage is metered by tokens, tool calls have a base cost, and each knowledge retrieval or document ingest costs a credit.
For exactly what consumes credits and how token usage is converted, see Credits & metering.

Plans and your allowance

Your plan decides your monthly credit allowance and your limits. The credit allowances below are the values ModuleX runs against.
PlanMonthly credit allowanceBest for
Free1,500 credits (one-time, to get started)Trying ModuleX on your own
Pro25,000 credits per monthIndividuals and small teams
Max100,000 credits per monthHeavy or team-wide usage
EnterpriseCustomOrganizations that need scale, SSO, and self-hosting
Each paid plan’s monthly allowance lines up with its monthly price at the 0.001percreditrate:Pros25,000creditsis0.001-per-credit rate: Pro's 25,000 credits is 25 of managed usage, and Max’s 100,000 credits is $100. The Free allowance is a one-time grant to get you started, not a recurring monthly reset.
ModuleX’s marketing site and its backend pricing configuration currently list two different annual prices for Pro and Max, and which one is authoritative is being confirmed. Always check the price shown at checkout before you subscribe to an annual plan. The credit allowances above are not affected by this — they are the same everywhere. See Plans & pricing for the full comparison and both annual figures.

Managed vs bring-your-own-key (BYOK)

ModuleX gives you two ways to use models, tools, and knowledge. The difference is who runs the work and who bills for it.

Managed usage

ModuleX provisions the model, tool, or vector store for you. This usage is metered in credits against your plan allowance and wallet. It is the default when you do not connect your own provider.

Bring your own key (BYOK)

You connect your own provider account. That usage is billed directly by the provider with no ModuleX credits charged — ModuleX records it for analytics only.
A simple way to remember it: if ModuleX runs it, it costs credits; if your own key runs it, it does not. You can mix the two — for example, use a ModuleX-managed model in one workflow and your own OpenAI or Anthropic key in another. Connecting your own providers is covered in LLM providers and Knowledge providers.

The wallet: covering work beyond your allowance

When your monthly allowance is used up, a paid organization can keep working by spending down a prepaid wallet.
1

Turn on overage

On a paid plan, an owner or admin enables overage for the organization. Until it is on, work stops once the allowance is empty rather than spending the wallet.
2

Top up the wallet

Add a prepaid balance. A 10topupadds10,000credits,atthesame10 top-up adds 10,000 credits, at the same 0.001-per-credit rate as your plan.
3

Let auto top-up keep it funded (optional)

Auto top-up can refill the wallet automatically when the balance gets low, so usage is not interrupted.
Overage and the wallet are paid-plan features. The wallet only comes into play after your plan allowance is exhausted — your monthly credits are always spent first. The exact top-up limits, the auto top-up defaults, and how a balance is reconciled are in Wallet & top-ups.

The usage gate: checked before work begins

Every piece of managed work passes through a usage gate before it starts. The gate confirms your organization can pay for the work — checking your plan allowance, your wallet, and your limits — and only then does the work run. This is why you are never billed for work that could not be admitted. The gate applies to ModuleX’s managed-usage surfaces:

Running workflows

Each managed workflow run is checked and metered before it executes.

The AI Composer

Turning plain English into a workflow runs through the gate per turn.

The Assistant

Each Assistant turn is admitted and metered before the agent acts.

Managed knowledge

Retrieval and document ingest on ModuleX-managed knowledge are metered.
When the gate declines work, the request comes back with a clear status: a 402 if your credits are exhausted or your wallet cannot cover it, a 403 if you have hit a plan quota, or a 429 if you have hit a rate limit. Everyday actions that do not run managed work — such as browsing your workflows or editing organization settings — are not gated and never return these billing responses. For the full response shapes and how to handle them, see Usage gating & limits and Errors & status codes.

Where billing lives

Billing belongs to the organization, not to an individual. The plan, the credit allowance, and the wallet are shared by everyone in the organization, and every run is metered against the organization it runs in. Managing the plan and the wallet is reserved for owners and admins — see Organizations, roles & membership.

Keep going

Plans & pricing

Compare Free, Pro, Max, and Enterprise — allowances, limits, and pricing.

Credits & metering

Exactly what a credit is and what consumes credits.

Usage gating & limits

The gate and its 402, 403, and 429 responses, in detail.

Wallet & top-ups

The prepaid wallet, manual top-ups, and auto top-up.

Credits & the billing model

The concept behind it all — how managed usage is metered and where the gate applies.

Trials & dunning

Free trials, grace periods, and what happens if a payment fails.