Processor cost preview and charge-level usage breakdown

Run responses now include a finer-grained credit breakdown. Each entry in usage.breakdown can now include a charges array that itemizes the cost drivers behind that run’s credits — for example base processor, review agent, or page-specific add-ons like agentic text correction. Each charge lists the billing product, unit (page or cell), quantity, credits consumed, and applicable page numbers when billing is page-scoped.

For background on billing units, see How credits work. For the run usage shape, see usage on the extract run response.

API — optional charges on each usage.breakdown entry with product, unit, quantity, credits, and page-level detail where applicable