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. The API initially launched with a single DPT model called . Because there was only one DPT, it was not surfaced to users. We are now introducing , which offers improved performance for complex tables, support for new chunk types (including barcodes and ID cards), and more precise captioning for figures. With multiple DPT models now available, you can now select a DPT in both the Playground and when calling the API directly.Important Considerations
is in Preview. This model is still in development and may not return accurate results. Do not use this model in production environments. The ability to select a is not available in the agentic-doc library. You can select a model in the Playground and when calling a parse API directly.DPT-1
is the original . It offers the basic ability to parse documents.DPT-1 Availability
The can be used in these API endpoints:- The “original” API
DPT-2
was introduced in September 2025. It builds upon , and offers these advanced features:- Agentic Table Captioning: DPT-2 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. DPT-2 can even detect stamps inside tables and process them separately—critical for compliance workflows.
- Expanded Chunk Ontology: Beyond text, tables, and figures, DPT-2 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 Availability
The can be used in this API endpoint:Set the Model in the API
When calling the , set the model using themodel
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
Why Model Versioning Matters
When integrating the API, you have two options for specifying the model:- Use a general model name (like
dpt-2
ordpt-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 - 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.
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.Model Versions and Snapshots
The following table lists the availablemodel
values for the API:
Model Values | Description |
---|---|
dpt-1 | Original parsing model. |
dpt-1-latest | Use the latest version of the dpt-1 model. |
dpt-1-20250615 | Use the snapshot released on June 15, 2025. |
dpt-2 | Updated parsing model. |
dpt-2-latest | Use the latest version of the dpt-2 model. |
dpt-2-20250919 | Use the snapshot released on September 19, 2025. |
Set the Model in the Playground
To toggle between different models in the Playground:- Load a document into the Playground.
- Ensure the Parse tab is open.
- Select the model you want to use from the top right corner.