ocr_engine, segment_processing, agentic_ocr, and merge_tables individually, you can apply a preset mode that bundles a recommended combination of all four. The parser ships with four:
Fast
Optimized for speed. Best for standard documents with clean text and simple tables.
Accurate
Balanced accuracy and performance. Ideal for complex layouts and detailed tables.
Agentic Lite
An agent reviews each segment, flags low-confidence text, and re-reads it against the source to resolve errors at faster speeds. Best for text-heavy documents.
Agentic
An agent reviews every segment, reasons over ambiguous or low-confidence text, and re-reads until resolved for maximum accuracy. Best for critical documents requiring the highest fidelity.
Choosing a Mode
The four modes trade speed for fidelity. The response shape is the same across them in most cases, though jobs submitted withmerge_tables (Agentic Lite and Agentic) can return a cached cross-page merged result instead (see the parse job status reference). Start with Fast and step up only when the output misses detail your pipeline depends on.
Mode Parameters
Each mode is shorthand for a specific set of parameters. To use a mode, pass the values from its column in your/parse request.
Modes are preset configurations. You can override any individual parameter after applying one. See the Parse API reference for the full parameter list.
Modes don’t set
segmentation_version — it’s orthogonal and composes with all four. Add segmentation_version=v2 to any mode above when the documents are forms and you want KeyValuePair segments. See Segmentation Version.
