A parser can read every word of a contract and still miss whether it was signed. Traditional OCR treats a stamp or a signature as noise, or as an unlabeled image blob. So a system can transcribe a permit or a certificate of origin end to end and never register whether it was signed, stamped, or sealed. For teams processing regulated paperwork, that is the one answer that matters. Agentic Document Extraction (ADE) closes the gap with attestation detection. At the parse stage, it finds these marks, assigns each a type, transcribes the text inside, and records where it sits on the page. Every mark comes back as one of four labels: SIGNED, E-SIGNED, STAMPED, or SEALED. Labels stack when a mark carries more than one, so an official filing stamped and signed in the same spot returns as [STAMPED][SIGNED]. The result is a queryable field, with grounding coordinates down to the line. "Is this document signed?" becomes a value your code can read, which lets you gate straight-through processing and route missing marks to a human automatically. One note for builders: attestation detection runs on DPT-3 Pro. Full breakdown, plus two real document examples, in the comments.

The documents worth automating are the ones you cannot afford to leak. A loan file carries income, identity, and account numbers on one page. A claims packet carries diagnosis codes. A utility contract carries pricing terms and counterparty data. Finance, insurance, healthcare, energy, and legal teams automate these workflows anyway. The volume leaves them no other option. Every vendor in that pipeline becomes another place your data lives. Security review starts there, long before anyone opens the accuracy benchmark. Agentic Document Extraction (ADE) is built for that review. Zero Data Retention, available on Team and Enterprise plans, processes your files in memory. Nothing is stored at rest. Nothing goes into model training. Your data stays in the region you pick, AWS US East or AWS EU. Encryption runs TLS 1.2 or higher in transit and AES-256 at rest. Enterprise teams can deploy ADE inside their own VPC. Every value ADE returns links to its place in the source document. That traceability is what a compliance reviewer actually asks for. Full detail on how we handle your data:

I love slots. I don't think people use them enough. If your design system feels rigid, this is probably why. Slots make it flexible without you having to predict every future need. More here:

Agentic Document Extraction (ADE) Parse returns three components: Markdown, structure, and metadata. Markdown is the full document as one string in reading order. Structure is a document tree of typed blocks with inline grounding. Metadata is a receipt tracking page counts, billing, and more. Five optional config options shape that output, each with a sensible default if you leave it out: page selection, table format, dropping a block from the Markdown string, per-line bounding boxes, and node-level Markdown. The video breaks down each one: