LlamaParse

Connect an agent via an official MCP server G

Agent access

Drive the product through a documented public API G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Build against official SDKs G

Agent access

Point an agent at llms.txt or agent-oriented docs G

Agent access

Run the product headlessly / in CI for automation G

Agent access

Subscribe to events via webhooks G

Agent access

Operate the product with natural-language commands G

Agentic features

Use an official CLI G

Agent access

Set up automations that run autonomously in the background G

Agentic features

Rely on versioned APIs with a documented deprecation policy G

Api quality

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Issue scoped/least-privilege API credentials for an agent G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Long parses run as async jobs with status polling and completion webhooks, so my pipeline never blocks C

Async

I supply a JSON schema and get back validated structured fields extracted from the document C

Schemas

Self-host the core product G

Uploaded documents get zero-retention handling with SOC 2 and HIPAA options, so I can process contracts and medical records C

Compliance

Export all of my data in open formats and leave G

Official typed SDKs for Python and TypeScript cover the full API — parse, extract, jobs — with sensible defaults C

Sdks

Complex tables — merged cells, nested headers, multi-page spans — come out as faithful HTML/markdown structure C

Tables

Output comes pre-chunked for RAG — semantic boundaries, metadata, embedding-ready segments — not a wall of text C

Chunking

Scanned and photographed documents OCR accurately — skewed pages, stamps, low quality scans included C

Ocr

The API parses complex real-world PDFs — multi-column layouts, headers, footers, footnotes — into clean, correctly ordered content C

Layout

Define rules that trigger actions automatically on events G

Prevent my data from being used to train AI models G

Multi-document packets are classified and split automatically — one upload, per-document results C

Splitting

One API handles my whole document mix — PDF, DOCX, PPTX, XLSX, HTML, images, email — without per-format plumbing C

Formats

Run the extraction stack in my own VPC or fully self-hosted when documents can't leave my infrastructure C

Deployment

Do everything through the API that I can do in the UI G

Every extracted field carries provenance — page number, bounding box, source snippet — so agents can cite and humans can verify C

Grounding

I get clean markdown/JSON designed for LLM consumption, with noise like repeated headers and page furniture stripped C

Output

Parsed output preserves document hierarchy — headings, sections, reading order — so downstream LLMs see structure, not soup C

Layout

Perform bulk operations across many items at once G

Choose where my data is stored (region/residency) G

Figures and charts are extracted or described (VLM summaries, image crops) with positions traceable back to the source page C

Figures

I turn extracted tables into typed rows/JSON I can load into a database without manual cleanup C

Tables

I push high-volume batches — millions of pages — with documented rate limits and predictable throughput G

Scale

Control data retention and deletion G

Thousand-page documents and multi-gigabyte files process reliably without timeouts or silent truncation C

Scale limits

Extractions carry calibrated confidence scores with a human-in-the-loop review path for low-confidence fields C

Review

Read the product's source under an open license G

Schedule recurring jobs or workflows G

A fast synchronous mode returns results in seconds for interactive apps, with latency documented per mode C

Latency

Non-English documents — including CJK and right-to-left scripts — parse with the same fidelity as English C

Languages

Opt out of telemetry and usage tracking G

I drag a document into a web playground and see parse/extract results before writing any code C

Playground

Handwritten fields and annotations are recognized and extracted, flagged with confidence when uncertain C

Ocr

The vendor publishes reproducible accuracy benchmarks and I can run my own evals before committing C

Evals

Version, review, and roll back my automations G