Credits explained

Credits are the unit of LLM and platform usage. They're token-based, not deliverable-based.

The 30-second version

Credits are debited as you run workrooms, revisions, and platform actions. There is no fixed "one deliverable = X credits" rule — the cost depends on the model, the input length, and the output length. As a rough heuristic, a typical proposal-style workroom lands in the 50-credit range, with each revision costing roughly 40% of the original (minimum 5). Monthly allowance credits reset every month and don't roll over. Top-up pack credits don't expire.

Why this matters

Some tools charge per deliverable, some per seat, some per token. AtelyaOS uses credits because deliverables vary wildly in size — a 3-bullet weekly recap and a 12-page proposal both count as "one deliverable" but cost very different amounts to produce. Credits track real usage.

The practical implication: a credit budget is more like a compute budget than a license. Plan for the typical month, and use top-ups when a quarter goes long.

How it works

What costs credits

Credits are debited when:

1. The Composer or another agent calls an LLM. Cost depends on the model used and the number of input + output tokens. The smallest charge is 1 credit per call.
2. A platform action runs. Specific platform actions (some scheduled jobs, some heavyweight integrations) have flat credit costs defined in ACTION_CREDIT_COSTS.
3. A revision round starts. Cost is max(5, ceil(workroom_total_credits * 0.4)). For a 60-credit workroom, that's 24 credits per revision.

Credits are not debited for:

• Exporting a deliverable to .docx or .pdf.
• Reading a workroom or activity log.
• Inviting a team member.

What a typical workroom costs

Realistic ranges, depending on inputs and model:

• A short weekly report (2–3 sections, no revisions): 15–30 credits.
• A standard proposal (4–6 sections, default model): 40–80 credits.
• A complex pitch deck script with multiple agents: 100–200 credits.
• A workroom with three revision rounds layered on top of a 60-credit draft: 60 + 24 + 24 + 24 ≈ 130 credits.

Watch the credit meter on the workroom detail page during execution to learn your team's actual numbers.

Monthly allowance vs. top-up

Two pools, separate behaviour:

The system spends from your monthly allowance first, then from top-up packs.

Running out

When your balance hits zero and a workroom needs more credits to continue, the workroom pauses on the in-flight task. From the billing page you can:

1. Buy a top-up pack. Instant. The workroom resumes when credits land.
2. Upgrade your plan. Lifts your monthly allowance. The new allowance is available immediately on the new billing cycle (proration depends on Stripe — see upgrade and downgrade).
3. Cancel and downgrade. If credits are not the right answer, downgrade or cancel. Your existing workrooms remain readable.

[SCREENSHOT: billing page showing credit balance and top-up button]

Where to watch credits

• Billing page — current balance, monthly allowance vs. top-up split.
• Workroom detail page — workroom_total_credits so far for that workroom.
• Activity log — every credit transaction, with which workroom or action triggered it.

Common pitfalls

• Treating one deliverable as fixed-cost. It isn't. Read the credit meter on a few finished workrooms to learn your team's real numbers.
• Counting on monthly allowance to roll over. It doesn't. Unused allowance vanishes at cycle end. Top-ups carry over.
• Not buying a top-up before a deadline. If you'll spike past your allowance this month, buy a pack now — workroom pauses are inconvenient mid-deliverable.
• Ignoring revision costs. Three revision rounds add up to roughly the cost of a second draft. Use them deliberately.

What's next

• Pricing plans — what each tier's allowance is.
• Credit packs — top-up sizes.
• Upgrade and downgrade — switching tiers when usage grows.