(ADE) is a document intelligence platform that converts documents into reliable, structured data. Use the structured data to build retrieval-augmented generation (RAG) applications, power intelligent search systems, extract key information, and automate document processing. This Preview introduces a redesigned Parse API powered by , our newest parsing model. is a complete rethink of document parsing for the era of AI agents and agentic workflows, designed around feedback from users running document-intensive workloads.Documentation Index
Fetch the complete documentation index at: https://docs.landing.ai/llms.txt
Use this file to discover all available pages before exploring further.
This is a Preview release. Don’t use it in production. See Important to Know for details. To learn more about the generally available (GA) version of ADE, go to ADE Overview.
What’s New in DPT-3
The new API is a redesign, not just a model update.- Designed for agent systems. Built around how downstream AI agents consume document data: stable element ids, predictable hierarchy, and Markdown span pointers so you can map results back to source.
- Hierarchical layout model. The structured output is a nested hierarchy: pages, elements on each page, lines within text elements, and cells within tables.
- Line-level visual grounding. Bounding boxes per element, plus per-line boxes for text elements, so you can highlight or extract content at the line level.
- Cleaner, more standardized Markdown. Standard Markdown image syntax for visuals, structured attestations and scan codes, standardized checkboxes, and figure subtype labels.
- Faster and lower-cost. Roughly twice as fast as , with complexity-aware pricing. See Pricing.
- New endpoint and response shape. Calls go to our new API. The response carries a hierarchical
structuretree alongside a flatgroundingmap keyed by element id. See the How Parse Works.
Important to Know About This Preview
A few things to keep in mind before integrating with the Preview.Don’t Use the New API in Production
The model and the new Parse API may change based on customer feedback. This includes the response shape, model behavior, and credit consumption rates. Don’t run production workloads on the Preview API. The current GA version of ADE remains available; for production use, see ADE Overview.Using the New API Requires Changes to Downstream Code
The endpoint, request shape, and response shape have all changed from the GA Parse API. Existing pipelines that call the GA/v1/ade/parse endpoint need code changes to use the new /v2/ade/parse endpoint. See the Migration Guide for the full diff.
Not Compatible with the Other ADE APIs
ADE Extract and ADE Section consume Parse output and expect the GA response shape. If your workflow chains Parse with either of those, continue using the GA Parse API for those workflows.Not Available in the Python or TypeScript Libraries
The ade-python and ade-typescript libraries don’t yet include the new Parse endpoint. To use , call/v2/ade/parse directly with cURL or your HTTP client of choice.
Only PDFs and Images Are Supported
The new Parse API supports PDFs and images only. For other file types, keep using the GA Parse API. See Supported File Types for the full list.Password-Protected Files Are Not Supported
The new Parse API does not support password-protected files. Decrypt the file and submit an unencrypted copy, or use the GA Parse API.Find What You Need
Pick a starting point based on what you want to do.Try It in the Playground
See in action without writing code. Upload a file in your browser.
Quickstart (API)
Make your first API call in under five minutes.
How Parse Works
Understand the response shape: pages, elements, and grounding.
Migrate from GA
Already using the GA Parse API? See what’s changed.