CodeCleared credits

Understand CodeCleared core and SAST credit pools, included plan allowances, and pay-as-you-go rules.

Purpose

Credits fund eligible scans and are tracked separately for core and SAST work.

Who

Organization owners and billing owners.

Prerequisites

Open Billing for the current organization before scheduling high-volume scans.

How it works

Review the available core and SAST pools, then select scan types that use the relevant pool.

Organization owners and admins can open Settings → Billing → History to see the ledger of credit movements (newest first): grants, consumption, purchases, coupons, and period resets. Each row shows pool, type, amount, balance after, project unit (link when available), trigger (sourceTrigger, for example manual-ui, scheduled, api, cli, push, bulk-ensure-pack, bulk-ensure-report, bulk-ensure-sbom), and sanitized details (scan type or a support adjustment motif). Rows written before this enrichment may omit project unit and trigger. Export to CSV is available from the same view. On a client organization, the ledger shows the parent billing account (client orgs have no separate credit pool).

A billable scan consumes a credit after preflight succeeds (repository access and required inputs such as a lockfile or SBOM are available), immediately before the scanner runs. Setup failures (missing PAT, inaccessible repo, missing lockfile, and similar) do not consume credits. If a scan fails with a platform fault after debit (system_error or workflow_timeout), History may show an automatic grant with source=scan_failure_refund and a customer-visible motif restoring that consume.

Evidence refresh (optional before Reports / SBOM / Auditor Export Pack) bills missing/stale scans via those bulk-ensure-* triggers. Assembling the report, SBOM merge, or auditor ZIP does not consume credits.

Ledger types:

Type	Meaning
`grant`	Manual or system grant (including support goodwill)
`consume`	Credits spent (usually scans)
`purchase`	Credit pack purchase
`coupon`	Coupon redemption
`period_reset`	Included-period allowance (plan or SAST mid-cycle)

Support adjustments appear with source=cc_admin_remediation and a customer-visible motif. They are also reflected in organization audit logs under the billing category. Automatic platform scan refunds appear as ledger grants with source=scan_failure_refund (History only — not an AuditLog event). CodeCleared platform administrators can inspect read-only auto-recharge settings for core and SAST pools (enabled, threshold, pack, caps, last status/error, failure backoff) in the CC Admin credits snapshot — no Stripe customer or payment-method identifiers are exposed.

Business rules

Free includes 100 core credits. Starter includes 800. Team includes 100 core credits per active license with a five-license minimum. SAST is a separate add-on pool. PAYG is available on Starter and above, not Free. On paid plans, billing admins may opt in to auto-recharge per pool — core and SAST independently (see Billing).

Scenarios & edge cases

Core credits available but SAST fails: add SAST entitlement or credits. Team below five active licenses: it does not meet the plan minimum. seat_license_required: see Credits and 402. Support-triggered scan: a scan started by a CodeCleared platform administrator does not consume your core or SAST pools; audit metadata may include creditFree — see Audit logs.

Limits

Balances, pricing, and final entitlements shown in Billing are authoritative.

Common errors

Treating core and SAST credits as interchangeable.
Expecting PAYG on Free.