Skip to main content

Parsing Models Overview

A (DPT) is the model that powers the parsing capabilities of the ADE Parsing APIs. The DPT identifies document layouts and chunks, then generates descriptive explanations (captions) for those chunks.

Availability

The ability to select a is available:

Model Versions and Snapshots

The following table lists the available model values for the and ADE Async Parse API:
The dpt-1 and dpt-2-mini models are deprecated. Use dpt-2 instead.

Why Model Versioning Matters

When integrating the API, you have two options for specifying the model:
  1. Use a general model name (like dpt-2 or dpt-2-latest) to always get the newest version. This automatically give you improvements and updates, but parsing results may change when new model versions are released
  2. Use a specific snapshot (like dpt-2-20250919) to pin to an exact model version. This ensures consistent parsing results over time, but you won’t receive improvements.
If you use only a general model name like dpt-2 in production, your application may produce different results when we release model updates. Consider whether you need consistent results or prefer to receive the latest improvements.

Understanding Snapshots and -latest

Snapshots are frozen versions of a model released on specific dates. Each snapshot maintains the same parsing behavior indefinitely, making your results predictable. The latest suffix always points to the most recent snapshot of that model.

DPT-2

was introduced in September 2025. It builds upon an earlier model, and offers these advanced features:
  • Agentic Table Captioning: can parse large, complex, no-gridline, and merged-cell tables with unprecedented fidelity. Every cell is preserved, aligned, and made accessible—enabling cell-level grounding so you know exactly where values came from.
  • Refined Figure Captioning: Logos, seals, and small figures are now identified precisely and concisely, eliminating the noise of verbose descriptions.
  • Smarter Layout Detection: Fewer chunks are missed, even in messy scans. can even detect stamps inside tables and process them separately—critical for compliance workflows.
  • Expanded Chunk Ontology: Beyond text, tables, and figures, now recognizes attestation (signatures, stamps, seals), ID cards, logos, barcodes, and QR codes—ensuring all document elements are classified consistently. To learn more, go to Chunk Types.

dpt-2-20260410

The dpt-2-20260410 snapshot builds on previous snapshots with these improvements:
  • Improved cell parsing in forms and tables: Text positioned at different locations within a cell is now captured more completely.
  • Improved column alignment in complex tables: Cell data now more accurately aligns with its corresponding column headers.

dpt-2-20260302

The dpt-2-20260302 snapshot builds on previous snapshots with several improvements, including:
  • Table boundary detection: Tables that were previously split into multiple chunks are now correctly identified as a single table.
  • Improved large table accuracy: Large tables are now parsed more accurately.
  • Special characters returned as Unicode: Characters such as asterisks are now returned as their Unicode characters (for example, *) rather than as spelled-out strings like asterisk.

DPT-2 Availability

The can be used in these API endpoints:

Set the Model in the API

When calling the or ADE Parse Jobs endpoint, you can set the model using the model parameter. If you omit the model parameter, the API will use the latest snapshot of the dpt-2 model. For example, run the command below to use the latest snapshot of .

Set the Model with the Library

When using the library, you can set the model using the model parameter in the parse() function. If you omit the model parameter, the library will use the latest snapshot of the dpt-2 model. For example, use this code to parse a document with the latest snapshot of :

Set the Model in the Playground

To select the parsing model in the Playground:
  1. Open a project in the Playground.
  2. Click the Parse tab.
  3. In the top-right corner of the parse result panel, click Config.
  4. From the Model drop-down, select the model you want to use.
  5. Click Re-run all files. Configure Parse Settings
Switching the model re-parses every file in the project. If you switch back to a model that was already applied to the project, the Playground reuses the cached parse results instead of re-parsing.