How credits work
Credits are held and reported at workspace level. Parsing and model-assisted analysis consume credits according to the active platform price configuration. DocIQ shows an estimate before a run starts, but final usage can vary with document length and processing needs.
The credit lifecycle
- DocIQ estimates the maximum expected cost for the requested work.
- Starting the run places a hold so concurrent runs cannot spend the same balance.
- Each metered operation is recorded in an append-only ledger.
- When processing finishes, actual usage is settled and unused held credits are released.
- If work stops, the system settles completed usage and releases the remaining hold according to the run state.
Monitor usage
- Open Settings, then Credits to see available, reserved, and total balance.
- Use usage analytics to compare time periods, capabilities, and operations.
- Investigate unexpected burn before starting a large batch.
- Keep purchase and adjustment records with the workspace audit trail.
Reduce avoidable usage
- Remove accidental duplicate files before a run.
- Confirm candidate grouping and criteria before analysis.
- Use revisions and resume controls instead of recreating a whole run after a transient failure.
- Test a new workflow with a representative small batch before scaling it.