How credits work
Juma runs on one pool of credits per workspace. A credit meters the tokens each model call sends and receives, at a published weight for every model.
What is a Juma credit?
One pool per workspace
Every member draws on the same balance. Usage shows per member, model, tool and project.
Unlimited seats
Adding a teammate changes nothing on the invoice. Running more work does.
Weighted per model
Each model has a published weight in credits per million tokens. The table below is the ledger.
What does each model weigh?
Each model carries a published weight in credits per million tokens, with input and output priced separately. The weights below apply to every workspace on a credit plan. Claude Opus weighs about 1.7 times Claude Sonnet. Gemini 3.1 Pro weighs about two thirds of Sonnet.
The table is a ceiling, not a forecast: prompt caching, context compression and model routing mean a workspace's effective consumption runs below a raw token calculation. GPT-5.6 Terra is the default model for new workspaces; workspace admins can change the default, and any member can pick a different model for a chat.
The weights are the same for every workspace. When a weight changes, the table changes with it and the date above moves. New models are added with their weight at launch. Changes to the credit price itself are announced to workspace admins by email in advance.
What does a Flow run actually consume?
A Flow run is a chain of model calls. Each call sends the conversation so far, the project's instructions and any tool results to a model, and gets text back. Credits count those tokens at the model's weight. Three real runs from our own workspace show the scale: 14 calls for a case study, 35 for an ads audit, 67 for a cross-channel performance analysis.
Customer case study
14 model calls · no integrations · 436,000 input tokens · 5,200 output tokens · GPT-5.6 Terra
Google Ads waste audit
35 model calls · Google Ads, 3 calls · 1,160,000 input tokens · 16,500 output tokens · GPT-5.6 Terra
Campaign performance analysis
67 model calls · Google Ads 2 calls, Meta Ads 2 calls · 3,180,000 input tokens · 25,900 output tokens · GPT-5.6 Terra
Measured in our own workspace, August 2026, each on a single pass with no revisions. Same model for all three, so the difference is the work: more calls, more context carried into each call, more data from connected tools, and a longer deliverable at the end. Integrations and MCP tools have no price of their own; the calls they trigger are metered like any other. Run the same Flow on Claude Opus 5 and the Opus weights apply instead. The same Flow costs more with a longer brief, deeper research, more revisions or a longer deliverable. Image generation, web search and light models bill by consumption at smaller weights. The usage page in workspace settings shows what each run cost, per member, model, tool and project.
Why do Flows use fewer credits than long chats?
The project holds the what, the Flow holds the how, and they stack. Strategy, taste and judgment stay with the team.
Save recurring work as a Flow
The trial-and-error gets paid for once, when the Flow is saved, not every time the task comes round.
Start a fresh thread for a new task
A thread that has been running all week carries all week's context into every call.
Keep project knowledge lean
Instructions and knowledge ride along on every call in the project. Ten focused pages beat a hundred loosely related ones, for quality and for credits.
What happens to unused credits?
A light month is not lost: whatever is left in August is there in September. It does not stack beyond that. If the balance keeps carrying over, the plan is too big; if the team tops up every month, it is too small.
Plan credits, monthly or annual
Valid for the billing month plus the following month.
Top-up credits
Valid for 12 months from purchase. They survive plan changes.
Referral credits
No expiry.
What happens when the balance runs out?
Top up anytime
Packs run from 1,000 to 30,000 credits, purchased in billing settings. Top-up credits last 12 months.
Auto top-up
Set a threshold and an amount. When the balance drops below the threshold, Juma adds the pack and emails the admins. No conversation waits.
Resize the plan
Plans move up anytime and down from the next billing cycle. A team that tops up every month is better off one plan size up.