Credits

Credits are the only unit ClawsGO charges in; 3,000 credits correspond to one US dollar. Plans grant credits every month, top-ups and rewards arrive as credits, and model calls and per-use services in your tasks are deducted from them.

Monthly and permanent credits

Your balance has two parts:

• Monthly credits: granted every 30 days from the day you bought the plan, independent of calendar months. On a monthly plan they are valid for that cycle and whatever is left expires at the end; on a yearly plan, leftovers roll into permanent credits.
• Permanent credits: top-ups, signup credits, referral rewards and yearly rollovers. They never expire.

Monthly credits are spent first, then permanent credits. After a plan ends, permanent credits keep working with Free-tier models only.

How model usage is metered

cost = input × input rate + cached input × cached-input rate + cache writes × cache-write rate + output × output rate

• Four rates: every model has its own rates for input, cached input, cache writes and output, and the gap between models differs by lane. Cached input costs far less than normal input. Caching is automatic; there is nothing to configure.
• The reference multiplier at the end of each row in the model menu is roughly what the model costs on a typical task relative to ClawsGO 1.0 Lithium (x1.0), for example Claude Sonnet 5 x2.0, Claude Opus 5 x5.0. It is a guide only: actual charges follow the rates above, and the real ratio shifts with a task's token mix. The full table is in Choose a model.

The 1M context window and cluster mode carry no feature fee, but the first feeds the model more per turn and the second runs several subagents, so a task's total consumption rises.

Per-use services

Failed or interrupted tasks

Charges follow usage that actually happened, not whether the task finished. If you stop or interrupt a task, what it already used is still deducted. If a task fails because of a fault on our side, open a ticket under Settings → Tickets and the credits are returned once confirmed.

Running out

If the balance is too low when you send, the message is not sent and "Not enough team credits" appears above the composer. If the balance runs out mid-task, an "Out of credits" card appears at the end of the reply; the work so far is safe. Top up or upgrade, then reply "Continue".

Team owners can set each member a credit limit per 30-day cycle. A member who reaches it sees "Your spending limit for this cycle has been reached" and is paused until the next cycle or a higher limit.

Viewing usage

Open Team & Subscription → Usage for this cycle's spend and the projected days until it runs out. "Full usage" opens the dashboard: 7, 30 or 90 days, by day, by member, by model and by conversation, with credits, requests and token mix, and "Export CSV".