Skip to main content

Understanding Credits & Usage

Credits are how MOD meters compute. This page explains exactly what they cost you and how to stay in control — because nobody likes a surprise bill.

What a credit is​

  • Your plan includes a monthly credit allowance (e.g. Free = 100, Starter = 1,000 — see the Billing FAQ).
  • The allowance resets each billing cycle — unused credits don't roll over.
  • Each node run costs a small number of credits (typically 0–3), set per node. Lightweight nodes (inputs, simple converters) are often 0.

What consumes credits​

  • Running a workflow charges the credits for the nodes that execute.
  • Batch mode charges per file — a 200-image batch runs the workflow 200 times. Budget accordingly.
  • Idle time, uploads, downloads, and just building a workflow cost nothing — only actual node execution does.

How to monitor it​

  • Dashboard → Billing shows your credit usage for the current cycle.
  • Analytics & System breaks usage down over time and by workflow/node, so you can spot an expensive node. See Analytics.
  • Before a big batch, glance at your remaining credits.

How you avoid surprises​

MOD is conservative by default:

  • Overage is OFF by default. When you exhaust your monthly credits, work simply stops until the next cycle — you are not silently billed extra.
  • To let work continue past your allowance, a paid plan can opt in to overage, billed at your plan's per-credit rate.
  • Even with overage on, a platform admin can set an overage cap to bound the maximum extra spend. See Overage caps.
  • The Free plan can't enable overage at all — it's a hard stop, so it can never cost you money.

Quick answers​

  • "Will building/experimenting cost me?" — No. Only running nodes costs credits.
  • "What if I run out mid-batch?" — With overage off, remaining files wait for the next cycle (or an upgrade). With overage on, they continue at your per-credit rate (up to any cap).
  • "How do I see what's expensive?" — Analytics → usage by node.