> ## 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.

# Overview

> Learn what DPT-3 changes about document parsing and how the Parse v2 API works.

export const dpt2 = 'DPT-2';

export const dpt3 = 'DPT-3';

export const parseDpt3 = 'Parse';

export const ade = 'Agentic Document Extraction';

[{ade}](https://ade.landing.ai/) (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.

The [Parse v2 API](https://docs.landing.ai/api-reference/parse/ade-parse) is powered by **{dpt3}**, our newest parsing model. {dpt3} 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.

## What DPT-3 Changes

The Parse v2 API is a redesign, not just a model update.

* **Designed for agent systems.** Built around how downstream AI agents consume document data: semantic block ids, predictable hierarchy, and Markdown ranges so you can map results back to source.
* **Hierarchical layout model.** The structured output is a nested hierarchy: pages, blocks on each page, and cells within tables.
* **Line-level visual grounding.** Bounding boxes per block, plus per-line boxes through each block's atomic grounding, so you can highlight or extract content at the line level.
* **Cleaner, more standardized Markdown.** Structured figure elements with classification labels, bracketed attestation and scan-code labels, and standardized checkboxes.
* **v2 endpoint and response shape.** Calls go to the [Parse v2 API](https://docs.landing.ai/api-reference/parse/ade-parse). The response carries a hierarchical `structure` tree in which every block holds its own location data. See [Parse API Response](./parse-response).

## Important to Know

A few things to keep in mind before integrating with the Parse v2 API.

### Using the Parse v2 API Requires Code Changes

The endpoint, request shape, and response shape all differ from the Parse v1 API. Existing pipelines that call the v1 `/v1/ade/parse` endpoint need code changes to use the v2 `/v2/parse` endpoint. See the [Migration Guide](./migration-guide) for the full diff.

### Not Compatible with the v1 ADE APIs

The v1 [ADE Extract](/ade/ade-extract) and [ADE Section](/ade/ade-section) APIs consume Parse output in the v1 response shape. To extract fields from Parse v2 output, use the [Extract v2 API](./extract), which works on the v2 Markdown. If your workflow uses Section, keep that workflow on the Parse v1 API.

### Only PDFs and Images Are Supported

The Parse v2 API supports PDFs and images only. For other file types, use the Parse v1 API. See [Supported File Types](./file-types) for the full list.

### Password-Protected Files Are Not Supported

The Parse v2 API does not support password-protected files. Decrypt the file and submit an unencrypted copy, or use the [Parse v1 API](/ade/ade-parse-password).

## Find What You Need

Pick a starting point based on what you want to do.

<CardGroup cols={2}>
  <Card title="Try It in the Playground" icon="play" href="./playground">
    See {parseDpt3} in action without writing code. Upload a file in your browser.
  </Card>

  <Card title="Quickstart (API)" icon="code" href="./quickstart">
    Make your first API call in under five minutes.
  </Card>

  <Card title="How Parse Works" icon="diagram-project" href="./parse">
    Understand the response shape: pages, blocks, and grounding.
  </Card>

  <Card title="Migrate from v1" icon="arrow-right-arrow-left" href="./migration-guide">
    Already using the Parse v1 API? See what's changed.
  </Card>
</CardGroup>