How to keep ClearRun credit use predictable

Score only the answers that matter, keep CI sample sets small and fixed, use mock mode in tests, and check Usage history each week. Per-call costs are on the pricing page.

Last updated

Habits that help

  • Mock mode for tests. No credits. See How to use ClearRun mock mode in Jest or Vitest tests.
  • Fixed CI sets. Score the same small folder each run.
  • Run CI on relevant changes only. Use path filters.
  • Lookups are free. Use verify instead of re-scoring.
  • One key per use. Usage history shows which key made each call.

Watch it

Usage history and its CSV show time, kind, credits and key for every paid call.

When you run out

Calls are refused with 402, not charged. See What happens when I run out of ClearRun credits?