Docs/Concepts/Credits
Reference

Credits

IDPForge meters work in credits, not pages. Every job reserves credits up front, settles to what it actually used, and returns the rest — and a failed job costs nothing.

Credits, not pages

IDPForge charges in credits. A credit is a unit of compute, so a dense page that needs a larger model costs more than a simple one — pages are a rough headline, credits are the real measure. Your balance, what is reserved, and what each pipeline and stage consumes are all shown on the billing dashboard.

The billing dashboard. The balance shows credits available and credits reserved by in-flight jobs; the analytics below break consumption down by pipeline and by stage.

Reserve, settle, release

Every job moves through the same three steps.

01
Reserve
Credits are held before the job is queued
02
Settle
On success, the charge is the actual cost, capped at what was reserved
03
Release
The unused remainder returns to your balance

Because the charge is capped at the reservation, a job can never cost more than it reserved. And a job that fails releases its whole reservation — a failed job costs nothing.

When the balance is empty

A reservation needs a sufficient balance. When there is not enough, the submission is rejected with HTTP 402 Payment Required and no job is created — nothing is queued to run later against credits you do not have. See Submit a job.

How consumption is metered

Consumption is tracked per stage, so the dashboard can show where credits go — Parse / OCR, Split & classify, Extract, autofill, storage and API. This is why a pipeline that only classifies costs a fraction of one that extracts every field.

Buckets

Credits are drawn in order, and free credits are spent before paid ones.

BucketBehaviour
FreeGranted credits; spent first.
SubscriptionYour monthly amount; renews each cycle.
Top-upOne-time purchases; roll over.
OverageAn optional paid allowance beyond the above, up to a cap you set.

Held credits

A job that stops midway — blocked, or partially complete — holds its reservation so a fix-and-re-run can resume it rather than paying twice. You can release held credits from the Jobs view, discard the job to reclaim them, or let them return automatically after a hold expires.

Overage

Overage is off unless you set a per-cycle spending cap. With a cap set, jobs can continue past your subscription and top-up balance up to that limit, billed at cycle close. With no cap, an empty balance simply returns 402.

An auditable ledger

Every grant, top-up, reservation, settlement, and adjustment is written to a ledger, and each row records the pricing in force at the time. The credit activity history on the dashboard is that ledger.

Was this page helpful?
Last updated 19 Aug 2026