Billing, credits, and limits
How runs are paid for: credits, subscription plans, concurrent-run and scope limits, automation caps, private runner access, refills, and invoices.
NullSquare uses two layers of billing. Credits are the unit of consumption — each run draws on the balance as the agent does work. Your subscription plan sets the entitlements that apply on top of credits: how many runs can execute concurrently, how many active scopes you can have, whether automations and private runners are enabled.
This page is the operational reference for both layers — what each control does, where to find it in the app, and what to expect when limits or balances are hit.
What you will learn
- Credits. What they are, how runs consume them, where to see the balance.
- Subscription and plan. The entitlements your plan grants beyond raw credits.
- Limits. Concurrent runs, active scopes, automation caps, private runner access.
- Refills and invoices. How to top up, where invoices live, and who can change billing.
Related app areas
Two layers — credits and plan
Credits are consumable. They are what a run actually spends. A small discovery on a small scope costs less than a deep authenticated assessment on a multi-tenant API; credit usage is shown on every run's detail page.
A plan is the wrapper. It defines how the platform behaves at scale — concurrent capacity, automation availability, runner access, refill cadence. Two organizations with the same credit balance but different plans will behave differently.
How credits work
Credits are consumed as the agent performs work, not at the end of a run. A long-running assessment draws steadily; a short one draws a small amount. Cancelling a run stops consumption but does not refund credits for work already performed.
- Each run shows its credit usage on the run detail page.
- The current balance lives in Settings → Billing.
- Discarded plans (from Safe Mode approval) do not consume credits.
- Assistant chat, viewing assets and findings, reading reports, and configuring scopes do not consume run credits.
- When the balance approaches zero, automations are paused before depletion to avoid surprise stoppages.
Plan limits
Your subscription plan grants entitlements that apply across the organization. Different plans unlock different limits — the current values are shown on Settings → Billing and on the Pricing page.
- Concurrent runs — how many assessments can execute at the same time. Additional launches queue until capacity frees.
- Active scopes — how many scopes can exist in parallel before requiring a plan change.
- Automation availability — whether scheduled and event-driven automations are enabled at all.
- Automation caps — how many active automations can run on a single scope or organization-wide.
- Private runner access — whether your plan includes the runner program for internal-network work.
- Concurrent runner capacity — how many private runners can be deployed against the organization.
Refills and recurring credits
Plans come with a recurring credit grant that lands on each billing cycle. If you need more before the next cycle, refill from Settings → Billing. Refills are pay-as-you-go and stack on top of the recurring grant.
- Refills are processed by the billing provider; the credit balance updates immediately on success.
- Auto-refill thresholds (if enabled) keep automations running through cycle boundaries.
- Only Owner and Admin roles can initiate refills or change billing settings.
Invoices and the billing portal
Every refill and every subscription renewal generates an invoice. Find them in Settings → Billing → Invoices, or click through to the billing portal for payment methods, billing address, and tax details. Invoices are downloadable as PDF for accounting handoff.
What happens at limits
The platform fails safely when limits are hit. Knowing the exact behavior prevents confusion when a run does not start.
- Out of credits — new runs are not launched; running runs continue but automations pause. Refill or wait for the next cycle.
- At concurrent-run limit — new runs queue and start as capacity frees.
- At active-scope limit — new scope creation is blocked; archive an unused scope or upgrade the plan.
- Automation cap reached — new automations cannot be enabled; existing ones continue to fire.
- Private runner not on plan — runner deployment is disabled; the runners page explains how to upgrade.
Who can change billing
Only Owner and Admin roles can change plan, refill credits, view invoices, or modify payment methods. Lead and Member roles can see balance and limits but not the billing portal. This separation keeps financial control with account governance.
Intelligence categories
The product selector on a run exposes intelligence categories — which capability tier the agent should operate at. Billing entitlements and the platform manage which categories are available; you choose between them by name, not by specifying a model.