Changelog

Parse runs now include minOcrConfidence and avgOcrConfidence on chunk and block metadata — the minimum and average per-word OCR confidence across the words in that region.

Both fields are returned on every chunk and block, and are null when word-level confidence isn’t produced for that region. Values are in the range 0–1.

For word-level confidence scores, set returnOcr.words to true.

For API version 2026-02-09, you can optionally pass generate on POST /extractors instead of supplying config. Provide one to five sample inputs as Extend file IDs or file URLs and Extend will generate a JSON extraction schema from those examples and return the extractor with the schema applied. Optionally add generate.instructions (up to 2,500 characters) to provide additional context about the document type or requirements for how values should be extracted. You cannot combine generate with cloneExtractorId or config.

• generate.files: 1–5 entries, each a file { id } or { url }.
• generate.instructions: optional free-text guidance to steer schema generation.

You can opt in to an advanced extraction setting that adds a fixed “current date” line to the system prompt. The model can use it when a field depends on today, relative phrases like “30 days from now”, or ambiguous short dates on the page (for example interpreting 02/03/26). The value is taken from when the run was created in UTC.

The option is off by default. For API version 2026-02-09, set advancedOptions.currentDateEnabled to true. See the JSON Schema extraction guide for how advanced options fit into your setup.

Run objects now include richer usage metadata so you can see how credits relate to underlying work alongside the billed amount (credits). The existing usage.credits value is unchanged. For full run payloads and webhook events, responses can also include totalCredits, representing all contributing charges for that logical run (for example extraction plus parsing when parsing was billed for that run), and a breakdown array listing each contributing resource type, id, and credit amount.

On list endpoints, summaries include credits and totalCredits but omit breakdown to keep payloads small. Runs written before totalCredits and breakdown were stored may expose only credits; treat totalCredits and breakdown as optional. For background on billing units, see How credits work. For the full object shape, see usage on the extract run response.

When bounding box citations are enabled on an extractor, you can set citationMode in advancedOptions to line, word, or block so citation polygons match the granularity you want. If you leave it unset, behavior matches what you have today (line-based citation processing plus block overlap handling across supported parse engines).

Extraction pipelines that use the parse 2.0.0-beta engine can now return bounding box citations for extracted values, so you are not limited to older parse versions when you need spatial references.

See Citations for how citations appear on extracted fields.

• citationMode — optional; configure in extractor advanced options in Extend Studio or on extractors (line, word, or block)

Two new endpoints make bulk background processing easier:

• /extract/batch — queue thousands of files for extraction in the background without running into rate limits.
• /parse/batch — bulk background parse operations.

Composer is now available for splitters, so you can optimize them automatically from eval sets. Previously, Composer was only available for extractors and classifiers.

If you’re working on splitting, check out our Splitter Benchmark to see how we evaluate models.