Skip to main content

Credits

Credits are the prepaid unit that funds the platform's AI features. Every plan includes a monthly credit grant, and you can purchase additional credits at any time.

What consumes credits​

  • Agent sessions — hosted agent runs (dispatch, routines, delegated sessions).
  • The workspace assistant — conversational turns and supervision.
  • Shell-layer baseline builds (stratus, stratus-coolify) — an agent builds these, so building a product from one debits a flat admission fee once per build; the build's own usage is zero-rated under it.
  • Orunbase-managed Cloudflare — each Cloudflare account Orunbase runs for you costs a small daily fee (33 credits a day), plus Workers usage beyond what Cloudflare's Workers Paid plan includes each month (10 million requests and 30 million CPU-milliseconds): 60 credits per extra million requests and 2 credits per extra million CPU-milliseconds. It is measured hourly and shows in your credit history as Managed Cloudflare. Your own Cloudflare connection costs no credits. See Orunbase-managed Cloudflare for the monthly cap and pauses.

Blueprint-driven baseline builds — every other baseline — do not consume credits: a runner executes them rather than a model, so they start and run whatever the balance.

Consumption varies with the model used, the baseline selected, and the size of the task. Sessions running on your own model API keys (a connected Anthropic/OpenAI/OpenRouter account) do not consume credits for model tokens — your provider bills those directly; the platform meters only its own compute.

Everything else — deployments, the catalog, logs, events, webhooks — does not consume credits. Those are covered by your plan's included allowances.

How the balance works​

  • Plan credits are granted at the start of each billing cycle and reset at the end of it — they do not roll over.
  • Purchased credits (top-ups) roll over and are consumed only after your plan credits, expiring 12 months after purchase.
  • The balance lives at the account: all workspaces under one account share a single balance, and each workspace's consumption is attributed in the credit activity view.

When the balance reaches zero, new agent sessions, assistant turns, and baseline builds are declined with a top-up prompt; running sessions are asked to wrap up gracefully — never cut off mid-action. Everything outside the AI plane keeps working.

Topping up​

Settings → Billing → Credits shows the balance, the current cycle's consumption, and the available top-up packs. A top-up is a one-time purchase through the same checkout as plan changes; credits arrive within a minute of payment confirmation.

Low-balance notifications​

When the wallet dips below the low-balance threshold, the platform emits a billing.credits.low_balance event — once per dip, re-armed when the balance recovers (a new grant or a top-up). Create a notification rule for that event type (Settings → Notifications) to get an email or Slack message before sessions start being refused. There is no automatic reload: credits are only ever purchased by an explicit checkout you confirm — topping up stays one click from the billing page.

For workspace admins​

  • The credit activity list shows every grant and consumption entry with its workspace attribution — amounts only, by design.
  • A declined action returns 412 credits_exhausted on the API, with the top-up path in the error payload.
  • Enterprise accounts receive pooled custom grants — talk to your account contact.