LandingAI

API-first Agentic Document Intelligence platform built for accuracy, reliability, and governance at scale.

[LandingAI @LandingAI]

We just launched a new short course with @DeepLearningAI

Document AI: From OCR to Agentic Doc Extraction.

This course shows how to move beyond OCR by building agentic document pipelines that preserve layout, reading order, and visual context when extracting structured data from complex PDFs and images.

Free to enroll here: https://t.co/GBrktZT7J2

[LandingAI @LandingAI]

https://t.co/iMNTj8n1UM

[LandingAI @LandingAI]

https://t.co/c8T0gqbEm4

[LandingAI @LandingAI]

Add it to your schedule here: https://t.co/XWkwEg7rKY

[LandingAI @LandingAI]

RAG on real documents is a different problem!

You can stand up a pipeline on clean PDFs. It breaks on dense tables, scientific figures, and irregular layouts.

Andrea Kropp is walking through the full workflow at @Snowflake Summit. ADE handles document parsing. Snowflake Cortex handles semantic retrieval, natural language queries, and agent orchestration. Everything surfaces through Snowflake Intelligence.

The entire stack runs from one SQL script and can be adapted to your use case in about half a day.

📅 Wednesday, Jun 3
🕓 4:00 PM - 4:45 PM PDT

[LandingAI @LandingAI]

Full breakdown: https://t.co/kzT3ie3Vcj

[LandingAI @LandingAI]

Extraction scales fine on short documents. Long documents break it.

Tables span pages and arrive as disconnected rows. Suppliers use different field labels and schemas start returning nulls. Compliance teams ask where a number came from and there's no answer.

These aren't edge cases. Long documents, label variation across suppliers, and audit requirements are standard in production workflows.

The new ADE Extract API handles this in two phases.

The Schema Building API ingests documents across suppliers and produces one master schema. It resolves label variation through semantic matching.

The Extract API processes the full document in a single call. Cross-page tables reconstruct as complete arrays. Every extracted value includes a chunk reference ID, so every number traces back to its source.

Link to the full article in the comments.

[LandingAI @LandingAI]

Case Study: https://t.co/Oh2AvHHzkp

[LandingAI @LandingAI]

GreenLite cut plan review turnaround by ~50% with LandingAI’s ADE.

@GreenLiteTech is an AI-native permit intelligence platform processing hundreds of construction projects monthly across hundreds of US jurisdictions.

Their Plan Review Agent reasons across building codes and assesses compliance across architectural disciplines. None of it works if extraction breaks.

Plan sets are dense, stylized, and inconsistent. Stamped drawings, multi-column specs, schedules that follow no template.

GreenLite evaluated frontier VLMs and several dedicated OCR and IDP providers. ADE was the most consistent performer on dense-figure and non-standard layouts.

The results:
→ 50% faster plan review turnaround
→ >90% precision and recall system-wide
→ ~90% of agent recommendations accepted by expert reviewers

Engineering shifted from extraction firefighting to reasoning and knowledge graph work.

Read the full case study.

Link in the comments!

[LandingAI @LandingAI]

Try it now in the playground: https://t.co/hsAmNxLfpC

Read more here: https://t.co/LV3rjrWwap

[LandingAI @LandingAI]

Your RAG pipeline reads every chunk. But it has no idea where they came from.

Introducing ADE Section: hierarchical context for every chunk in your retrieval pipeline.

Standard chunking strategies slice documents into fragments, stripping away structure. "Revenue is down 10%" lands in your index with zero signal of whether it came from Risk Factors or Global Operations. Both queries compete against the same flat pool of chunks.

ADE Section builds a hierarchical Table of Contents from your parsed document, tied to exact chunk anchor IDs. It prepends the full breadcrumb path to every chunk before embedding. Structure bakes directly into the vector.

The ancestor path saves as metadata, so you can filter retrieval to specific sections. A legal analyst searching for indemnification clauses doesn't need the system evaluating marketing copy. Precision filtering cuts noise on every query.

The breadcrumb travels with every chunk into the LLM. The model knows exactly where it is in the document. Citations hold up.

When the default hierarchy needs adjustment, pass a guidelines prompt in the API call.

Run ADE Parse, then run ADE Section.

[LandingAI @LandingAI]

Watch the full webinar: https://t.co/kmi3Bm1pE0

[LandingAI @LandingAI]

Unlocking RAG on Complex Documents!

Your RAG pipeline works on clean PDFs. It breaks on the documents you actually need to process. Scanned forms, nested tables, multi-page charts, irregular layouts. These are where conventional extraction fails.

Andrea Kropp from LandingAI and the @Snowflake team ran a webinar showing the full end-to-end workflow.

ADE parses complex documents. Dense tables, embedded figures, multi-page structures. It extracts structured fields and creates semantic chunks. Both get stored in Snowflake.

Snowflake Cortex provides the query layer. Semantic search across chunks for contextual questions. Natural language to SQL for structured queries on the extracted fields. External enrichment from sources like PubMed. Agents that orchestrate across all these capabilities.

Business users interact with everything through Snowflake Intelligence.

You'll see live demos on FDA regulatory documents and legal contracts. Andrea walks through the architecture, shows the code in Snowflake worksheets, and shares how Olas Medical deployed this in production.

Link to the webinar in comments.

[LandingAI @LandingAI]

Playground: https://t.co/hsAmNxLfpC

Read more here: https://t.co/YpxkT64VDQ

[LandingAI @LandingAI]

We are introducing ADE Classify.

Page-level classification for mixed documents.

Here's the problem. A 50-page mortgage PDF hits your pipeline. You pay to process 48 pages you didn't need. That mixed text reaches your extraction agent. It starts extracting invoice data from passport pages.

ADE Classify evaluates every page concurrently against your custom JSON class schema before ADE Parse even runs. Each page comes back with a label and a reasoning string.

Unknowns get flagged with a suggested class so nothing slips through silently. Pass semantic descriptions per class and the model handles the ambiguity - no fine-tuning needed to tell a formal invoice from a generic receipt.

Different document types route to different pipelines. Classification happens first, not after you've already paid to parse everything.

The reasoning string is logged for downstream auditing. Every routing decision your pipeline makes is fully traceable.

Try it right now in the Playground with your mixed documents. Link in the comments!

[LandingAI @LandingAI]

Agentic Loan Origination: https://t.co/czg2dzeYHu

[LandingAI @LandingAI]

We built a multi-agent loan underwriting system!

It's a production-ready multi-agent system powered by LandingAI Agentic Document Extraction (ADE) and Google ADK.

Upload a mixed financial document packet - pay stubs, bank statements, tax forms - and extract structured fields in one pass.

Here's the pipeline:

1. Parse the PDF page-by-page. Classify each page and group into logical documents.
2. Extract structured fields using document-specific schemas. Every field grounded to its exact location.
3. Claude agent applies underwriting rules - DTI ratio, income validation, fraud detection. Returns decision with reasoning.
4. Manager agent reviews the decision. Scores risk. Can override. Escalates edge cases to human review.

The best part: every extracted field is traceable back to its exact location in the source document. Bounding boxes. Confidence scores. Full visual grounding.

Extract once, then run unlimited scenarios. Change the loan amount or debt and get a new decision instantly without re-uploading.

Code is open source. Link in the comments!

[LandingAI @LandingAI]

Read more: https://t.co/qkGlXwbImq

[LandingAI @LandingAI]

ADE is now live on AWS Marketplace! 🚀

For teams already running on AWS, this means no separate procurement process or vendor approvals.

Deploy Agentic Document Extraction (ADE) against your existing committed cloud spend and go straight from evaluation to production.

ADE processes complex documents - financial reports, insurance claims, medical records - using a schema-driven approach that keeps context across pages and links every extracted value back to its exact source location in the document.

Supports cloud and VPC deployment for teams that need document processing to stay within their own infrastructure.

[LandingAI @LandingAI]

From Touchpoint to Outcome: Transforming Front-Office Processes with AI.

Join Neil Walker and Teon Rosandic on May 21 for a hands-on session on how to turn customer interactions into fully orchestrated, outcome-driven processes.

✅ Understand any document your customers submit with Agentic Document Extraction (ADE)
✅ Orchestrate end-to-end processes with OCTO by TCG Process
✅ Deliver faster, consistent, scalable customer experiences

Built for operations leaders, automation teams, and developers bringing document intelligence into production.

Thu, May 21 at 8AM PT. Free to attend.

[LandingAI @LandingAI]

AI Dev Day wrapped. 🎉

Two days in San Francisco. Over 3,000 developers showed up. The energy was high from the start.

David Park spoke on building agentic systems that work in production. His session focused on why document understanding is the foundational piece most teams skip.

He demonstrated a live multi-agent workflow analyzing documents. Real code. Real output. The audience was there for it.

Dan Maloney joined a panel talking about what's changing in software development. One takeaway: roles are blurring fast. Engineers aren't just coding anymore - they're making product calls, talking to customers, handling design questions. The job is different now.

At the LandingAI booth, people brought production problems. Complex tables spanning pages. Visual grounding for compliance. Hierarchies that get lost. Documents where structure matters as much as content. Cross-document reasoning. The pattern: LLMs and OCR models can extract text, but they can't see documents the way humans do.

Thanks to @AndrewNg for stopping by the booth, spending time with the team, and answering questions from developers. Great to see him engaging with the community.

Great to meet so many builders tackling hard problems.

Thanks to everyone who stopped by. Special thanks to @DeepLearningAI for organizing an incredible event