Document Extraction APIs Arena
LlamaParse vs Unstructured
LlamaParse wins · 16–12 (24 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round drawnAn llms.txt file is confirmed live via probe (HTTP 200), and LlamaIndex also documents an explicit 'for-agents' page with an MCP server and agent-oriented docs tools (search_docs, grep_docs, read_doc) designed for agents to consume documentation programmatically. missing for 10: independent/community confirmation that agents actually use llms.txt successfully in practice, and the docs-md alternate format probe returned 404 showing incomplete agent-doc surface.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.llamaindex.ai/llms.txt # LlamaIndex Documentation > LlamaIndex is a framework for building L…”
- [claimed-docs] “My agent should be able to search these docs”
- [claimed-docs] “The server ships with the following tools: 1. `search_docs` — a basic lexical search using BM25 2. `grep_docs` — exact search using regex 3.…”
- [claimed-docs] “search_docs — a basic lexical search using BM25 2. grep_docs — exact search using regex 3. read_doc — provides an interface to read the enti…”
- [probe] “official MCP server documented at https://developers.llamaindex.ai/for-agents/mcp/”
- [probe] “PROBE docs-md: HTTP 404 at https://developers.llamaindex.ai/llamaparse/.md”
A direct probe confirms llms.txt exists at docs.unstructured.io/llms.txt (HTTP 200) with agent instructions pointing to MCP server, SDK, and API docs, directly satisfying the story. Missing for 10: no evidence of additional agent-oriented doc formats (e.g., openapi.json, which probes show is 404) or third-party confirmation of agents successfully using the llms.txt file.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.unstructured.io/llms.txt # Unstructured > ## Agent Instructions > Fetch site content guidance and …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to UnstructuredLlamaParse offers a REST API, CLI, and SDKs (Python/TypeScript/Go/Java) suitable for scripted/CI use, plus webhooks for async job notification instead of polling, which supports headless automation workflows. Missing for 10: explicit CI/CD examples (GitHub Actions, Docker recipes), documented non-interactive auth/service-account flow for pipelines, and independent hands-on confirmation of headless CI usage.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
Unstructured exposes REST API and Python SDK callable via standard clients (cURL, Postman) and can build/trigger/monitor workflow jobs programmatically, enabling headless automation in CI pipelines. Missing for 10: explicit CI/CD documentation or example (e.g., GitHub Actions), and independent third-party confirmation of CI usage.
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnFirst-party docs explicitly describe an official MCP endpoint (https://mcp.llamaindex.ai/mcp) that exposes Parse, Classify, Extract, Split, and Index as callable tools for any MCP client, and a dedicated docs page details this server. Missing for 10: independent/hands-on confirmation that the MCP server works as documented and clarity on how it relates to the separate docs-search MCP tools (search_docs/grep_docs/read_doc) mentioned elsewhere.
- [claimed-docs] “https://mcp.llamaindex.ai/mcp is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index —…”
- [claimed-docs] “`https://mcp.llamaindex.ai/mcp` is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index…”
- [probe] “official MCP server documented at https://developers.llamaindex.ai/for-agents/mcp/”
- [claimed-docs] “The server ships with the following tools: 1. `search_docs` — a basic lexical search using BM25 2. `grep_docs` — exact search using regex 3.…”
Unstructured documents a dedicated 'Transform MCP server' that lets AI tools/agents (Claude Code, Cursor, Devin, etc.) ingest, partition, enrich, chunk, and embed local files directly through Unstructured, which is a first-party, officially supported MCP integration for connecting agents to the platform. Missing for 10: independent/hands-on verification of the MCP server working end-to-end and deeper API-level documentation beyond the overview page.
- [claimed-docs] “The Transform MCP server enables you to link your AI tools to Transform. You can then use your AI tools to have Transform ingest your local …”
- [claimed-docs] “This includes most AI code editors, IDEs, desktop assistants, and coding-agent frameworks. Tools such as the Codex CLI, Claude Code, Visual …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.unstructured.io/llms.txt # Unstructured > ## Agent Instructions > Fetch site content guidance and …”
ai-native userUse an official CLI
weight 2 · round to LlamaParseDocs mention the CLI as one of several supported interfaces to run parse jobs ('whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI') but no dedicated CLI reference, install instructions, or command examples are provided in the evidence pack. Missing for 10: CLI installation/usage docs, command examples, independent/community confirmation of CLI usage.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
Unstructurednone0/10The evidence pack documents a Python SDK, REST API, no-code workflow UI, and an MCP server for AI tool integration, but no official CLI tool is mentioned anywhere in the docs or probes.
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
- [claimed-docs] “The Transform MCP server enables you to link your AI tools to Transform. You can then use your AI tools to have Transform ingest your local …”
ai-native userDrive the product through a documented public API
weight 3 · round drawnLlamaParse offers a documented REST API plus SDKs (Python, TypeScript, Go, Java) and a CLI, with example code snippets for calling the parse endpoint, and webhook support for async job notification. Independent probes could not find a public OpenAPI spec, which slightly weakens strict machine-readability of the API. missing for 10: publicly discoverable OpenAPI/swagger spec, independent third-party confirmation of API robustness.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.llamaindex.ai/openapi.json, https://developers.llamaindex.ai/swagger.json, https:…”
Unstructured documents a public REST API and Python SDK with a comprehensive API reference covering jobs, workflows, partitioning, chunking, and enrichment, plus quickstarts and standard REST client support (cURL/Postman). missing for 10: a discoverable machine-readable OpenAPI spec (probe found openapi.json/swagger.json all 404) and independent third-party corroboration beyond vendor docs.
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnLlamaParsenone0/10Docs mention SSO and role-based access controls for managing org/project access (llamaparse-docs-9, llamaparse-docs-18), but there is no evidence of scoped or least-privilege API key/credential issuance specifically for agents (e.g., per-key permission scopes, agent-specific tokens). This is a fair axis for an API platform, so absence of evidence yields 'none' rather than 'na'.
- [claimed-docs] “Identity and access. Use SSO and role-based access controls to manage access to your organization and projects.”
- [claimed-docs] “Use SSO and role-based access controls to manage access to your organization and projects.”
ai-native userBuild against official SDKs
weight 2 · round drawnLlamaParse provides official SDKs across multiple languages (Python, TypeScript, Go, Java) plus CLI and REST API, documented with code examples (e.g., client.parsing.parse), and maintained as a public GitHub package (llama-cloud) with migration guidance. This directly supports building AI-native apps against official first-party SDKs rather than reverse-engineered clients. missing for 10: independent third-party benchmarking of SDK reliability/versioning, and no OpenAPI spec found (probe-3) to corroborate REST completeness
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [github] “Please migrate to the new packages: - **Python**: `pip install llama-cloud>=1.0`”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
Unstructured documents an official Python SDK for calling its API to partition, enrich, chunk, and embed files, alongside REST client support, and provides quickstarts specifically for building against it in ~5 minutes. Multiple docs pages (SDK overview, workflow build docs, quickstart) corroborate first-party SDK support with concrete code-level use cases. Missing for 10: independent/hands-on developer corroboration beyond vendor docs, and no publicly discoverable OpenAPI spec was found via probe.
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
- [claimed-docs] “Use Unstructured with Python to go from an unstructured source file to structured data output in about 5 minutes.”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
ai-native userSubscribe to events via webhooks
weight 2 · round to LlamaParseDocs explicitly describe configuring webhook endpoints to be notified when parse jobs complete, fail, or reach other states, directly matching the story. Missing for 10: independent/hands-on confirmation of webhook reliability, payload schema/signature verification details, and community corroboration of real-world webhook usage.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
Unstructurednone0/10No evidence pack item mentions webhooks or event-driven subscriptions; the API is described as job-based (trigger, poll status, download results) rather than push-based notifications. Missing for 10: any documentation of webhook registration, event types, or push notification mechanism.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to UnstructuredLlamaParsenone0/10LlamaParse/LlamaCloud is documented as a document parsing, extraction, classification, and indexing pipeline driven by user-defined schemas and rules, not a product that surfaces its own AI-generated insights or suggestions about the user's data inside a UI. Evidence covers extraction, classification, splitting, and RAG-indexing capabilities, but none describe an insights/suggestion feature (e.g., auto-generated summaries, anomaly flags, or recommendations) exposed to the user. missing for 10: any documented insights/suggestions UI or feature, evidence of autonomous analysis surfaced to users, independent confirmation of such a capability.
- [claimed-docs] “LlamaExtract provides a simple API for extracting structured data from unstructured documents like PDFs, text files, and images.”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
- [claimed-docs] “Generate extraction schemas with a prompt”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
Unstructured's docs use marketing language like 'discover hidden insights' when describing its connectors/data unification, and it does perform AI-driven extraction/enrichment (VLM-based table-to-HTML, structured JSON extraction) on data—loosely gesturing at 'insight generation.' However, there's no evidence of a dashboard, summarization, or recommendation feature that surfaces AI-generated insights or suggestions back to the user inside a product UI; the tool is positioned as an ETL/data pipeline for feeding RAG systems, not as a place where users consume AI-generated insights themselves. Missing for 10: a concrete insights/suggestions UI or feature, evidence of the product proactively surfacing analysis or recommendations to end users, and any hands-on/independent confirmation of such a capability.
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “It lets you define the target structure up front. Unstructured then extracts values in a consistent JSON format that matches your fields, re…”
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format. This table-to-HTML outp…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to UnstructuredLlamaParse supports asynchronous job processing with webhook notifications instead of polling, which enables integration into automated pipelines that run without manual monitoring, and MCP tool exposure lets agents trigger parsing autonomously as part of larger workflows. However, there's no evidence of native scheduling, cron-like triggers, or persistent background jobs that run independently of an external caller invoking them. Missing for 10: scheduled/triggered automation, autonomous recurring job execution, evidence of agents independently initiating parse jobs on a schedule.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “https://mcp.llamaindex.ai/mcp is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index —…”
- [claimed-docs] “`https://mcp.llamaindex.ai/mcp` is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index…”
- [probe] “official MCP server documented at https://developers.llamaindex.ai/for-agents/mcp/”
Unstructured's Workflow/Job APIs let users define workflows and programmatically trigger and monitor processing jobs (source-to-destination pipelines) via SDK/REST, which can be automated to run without manual intervention. However, there is no explicit evidence of built-in scheduling, event-based triggers, or persistent background automation (e.g., cron-like recurring runs) that would make the automation fully autonomous rather than externally triggered. missing for 10: evidence of native scheduling/triggers, autonomous recurring execution, and confirmation that jobs run without external orchestration.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “The Unstructured Pipelines workflow designer features a no-code user interface for transforming your unstructured data into data that is rea…”
- [claimed-docs] “Create a job to partition, chunk, and embed local files into AI-ready JSON with vector embeddings for semantic search.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnLlamaParsenone0/10LlamaParse's evidence describes it as a document parsing/extraction API (Parse, Extract, Classify, Split, Index) callable via SDKs, CLI, REST, or exposed to external agents via an MCP server — but there is no mention of a built-in AI assistant inside the product itself that a user could converse with or delegate tasks to. The MCP endpoint (llamaparse-docs-8/16/27) lets external agents call LlamaParse's tools, which is the reverse direction of this story.
Unstructurednone0/10Unstructured documents workflows, APIs, SDKs, and an MCP server that let external AI tools (e.g., Claude, Cursor, coding agents) call into the platform, but there is no evidence of a built-in AI assistant inside the Unstructured product itself that users can delegate tasks to.
- [claimed-docs] “Use Unstructured with Claude and plain language prompts to go from an unstructured source file to structured data output in about 5 minutes.”
- [claimed-docs] “The Transform MCP server enables you to link your AI tools to Transform. You can then use your AI tools to have Transform ingest your local …”
- [claimed-docs] “This includes most AI code editors, IDEs, desktop assistants, and coding-agent frameworks. Tools such as the Codex CLI, Claude Code, Visual …”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnLlamaParse supports several natural-language-driven controls: Classify uses natural-language rules, Extract can generate schemas from a prompt, and Parse output can be steered with custom natural-language prompts (e.g., focusing only on prices in a receipt). It also exposes an MCP endpoint so agents can invoke Parse/Classify/Extract/Split/Index via tool calls, which is agent-friendly but not itself a natural-language command interface. Missing for 10: a unified conversational/chat interface for operating the whole platform, and independent hands-on evidence confirming natural-language commands reliably control parsing behavior end-to-end.
- [claimed-docs] “Classify lets you automatically categorize documents into types you define (for example: invoice, receipt, contract) using natural-language …”
- [claimed-docs] “Generate extraction schemas with a prompt”
- [claimed-docs] “Guide parsing output with custom prompts. Extract specific data from a McDonald's receipt by instructing the parser to focus only on prices …”
- [claimed-docs] “https://mcp.llamaindex.ai/mcp is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index —…”
- [claimed-docs] “`https://mcp.llamaindex.ai/mcp` is the endpoint that exposes the platform's document processing — Parse, Classify, Extract, Split, and Index…”
Docs show a dedicated 'Claude and plain language prompts' quickstart and a Transform MCP server that lets AI tools (Claude Code, Cursor, etc.) instruct Unstructured to ingest and process files via natural language, which supports NL-driven operation. However, the core product remains API/workflow-designer driven, and most capabilities (job APIs, connectors, no-code UI) are not natural-language controlled. Missing for 10: independent/hands-on validation of NL command coverage across the full product, and evidence of NL control beyond the MCP/Claude quickstart path.
- [claimed-docs] “Use Unstructured with Claude and plain language prompts to go from an unstructured source file to structured data output in about 5 minutes.”
- [claimed-docs] “The Transform MCP server enables you to link your AI tools to Transform. You can then use your AI tools to have Transform ingest your local …”
- [claimed-docs] “This includes most AI code editors, IDEs, desktop assistants, and coding-agent frameworks. Tools such as the Codex CLI, Claude Code, Visual …”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round to UnstructuredLlamaParsenone0/10Docs show many static code snippets/examples (Python calls, curl-like usage) but there is no evidence of an interactive, runnable API reference (e.g., Swagger/OpenAPI explorer or live code sandbox); explicit probes for OpenAPI/Swagger endpoints returned 404s, indicating no such interactive reference exists.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.llamaindex.ai/openapi.json, https://developers.llamaindex.ai/swagger.json, https:…”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Guide parsing output with custom prompts. Extract specific data from a McDonald's receipt by instructing the parser to focus only on prices …”
Unstructured's docs include an 'api-reference' section with quickstarts that provide runnable Python/cURL/Postman code samples (e.g. docs-18, docs-31, docs-4/19/30), giving developers copy-paste examples to try. However, a direct probe for an OpenAPI/Swagger-style interactive spec returned 404 on all standard paths, indicating no live in-browser 'try it' API explorer exists — only static code snippets in prose docs. Missing for 10: a genuine interactive API console (e.g., Swagger UI/Redoc with live request execution), independent confirmation of an in-browser sandbox, and evidence the reference examples can be executed directly from the docs site rather than copied to an external client.
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “This quickstart partitions an example company annual report with a sample Python script and the Unstructured API.”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
- [claimed-docs] “From login to structured JSON in about 5 minutes, with Unstructured and Python.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnLlamaParsenone0/10LlamaParse exposes a REST API, but there is no evidence of a downloadable OpenAPI/Swagger spec; explicit probes for common OpenAPI endpoints (openapi.json, swagger.json, etc.) all returned 404.
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.llamaindex.ai/openapi.json, https://developers.llamaindex.ai/swagger.json, https:…”
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
Unstructurednone0/10While Unstructured documents a REST API and Python SDK, there is no evidence of a downloadable OpenAPI/Swagger spec; a direct probe for common OpenAPI paths (openapi.json, swagger.json, etc.) returned 404 on all candidates, confirming no machine-readable spec is publicly exposed.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnLlamaParsenone0/10No evidence describes a dedicated sandbox/test environment separate from production for LlamaParse; free credits and self-hosting/BYOC options are mentioned but do not constitute a documented sandbox mode for testing without touching production data.
Unstructurednone0/10The evidence pack shows free-tier trial pages, dedicated VPC deployment, and security/compliance certifications, but nowhere describes a distinct sandbox/test environment isolated from production data for API testing. Missing for 10: explicit sandbox or test-mode environment, staging API keys, or documented separation between test and production data flows.
- [claimed-docs] “Start processing your data with 10,000 free pages.”
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to LlamaParseThere is a version parameter in the parse API (version="latest") and a GitHub migration notice telling users to move to llama-cloud>=1.0, showing some versioning/migration practice, but no explicit documented deprecation policy, versioning scheme, or changelog is provided. missing for 10: a published API versioning scheme, a formal deprecation policy/timeline, changelog or release notes, and independent confirmation of stability guarantees.
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [github] “Please migrate to the new packages: - **Python**: `pip install llama-cloud>=1.0`”
Unstructurednone0/10No evidence of API versioning scheme (e.g. /v1/, /v2/) or a documented deprecation policy anywhere in the docs; OpenAPI spec probes also 404. missing for 10: explicit API version numbering, published deprecation/sunset policy, changelog for breaking changes.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to UnstructuredLlamaParse exposes a programmatic API/SDK plus webhooks so jobs can be automated at scale, and Classify lets rules be saved and referenced across multiple jobs, suggesting some bulk workflow support. However there is no explicit documentation of a batch/bulk submission endpoint, multi-file job queue, or bulk status/management UI for large sets of items. Missing for 10: explicit batch-submit API, bulk job dashboard/management, and independent evidence of large-scale bulk usage in production.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “Save reusable classification rules as a configuration and reference them by ID across multiple jobs.”
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
Unstructured's workflows/jobs API and connectors (35+ sources, 65+ file types) explicitly support ingesting and processing many files at once via automated pipelines, with job tracking, batch partition/chunk/embed operations, and SDK/REST access for programmatic bulk triggering. missing for 10: no explicit documentation of batch size limits, concurrency controls, or independent benchmarks of large-scale throughput.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “Create a job to partition, chunk, and embed local files into AI-ready JSON with vector embeddings for semantic search.”
- [claimed-docs] “Create a job to partition and enrich local files into AI-ready JSON with image descriptions, table HTML, named entities, and generative OCR …”
- [claimed-docs] “Ingest your files into Unstructured from Azure Blob Storage.”
- [claimed-docs] “Replace DIY pipelines: Move solutions into production faster. Reduce engineering costs. Eliminate maintenance. Resilient partitioning logic …”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to LlamaParseLlamaParse supports webhooks to notify on job completion/failure and saved reusable classification rule configs, which are event-trigger-like building blocks, but there is no evidence of a general rules engine where users define arbitrary conditions/triggers that automatically fire actions across the platform. missing for 10: a documented rules/automation engine, conditional trigger definitions beyond job status, and evidence of chained automated actions (not just notification via webhook).
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “Save reusable classification rules as a configuration and reference them by ID across multiple jobs.”
Unstructurednone0/10Unstructured's docs describe workflows that can be manually run or triggered via API/job calls, but there is no evidence of a rule-engine or event-based trigger system (e.g., 'run this workflow when a new file lands' or webhook-driven automation) that fires actions automatically on defined events.
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnLlamaParsenone0/10LlamaParse's evidence covers parsing, extraction, classification, splitting, webhooks for job status, self-hosting, and MCP tool exposure, but nothing describes native scheduling of recurring jobs or workflows (e.g., cron-like triggers or recurring pipeline runs). Webhooks only cover async notification for one-off jobs, not recurrence.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
Unstructurednone0/10The evidence describes creating, running, and monitoring workflows/jobs via API or no-code UI, but nowhere mentions scheduling or recurring/cron-based execution of these jobs. Absence of evidence for this applicable automation-depth capability means it is not shown to deliver.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “The Unstructured Pipelines workflow designer features a no-code user interface for transforming your unstructured data into data that is rea…”
ai-native userVersion, review, and roll back my automations
weight 1 · round drawnLlamaParsenone0/10No evidence of versioning, review workflows, or rollback for LlamaParse automations/configurations (e.g., parsing jobs, extraction schemas, classification rules). Only reusable configs via ID are mentioned (llamaparse-docs-39), but no version history, diff/review, or rollback capability is documented.
Deployment compliance — stories about deployment compliance in this arenaDeployment compliance
Stories about deployment compliance in this arena
Compliance
data engineerUploaded documents get zero-retention handling with SOC 2 and HIPAA options, so I can process contracts and medical records
weight 3 · round to LlamaParseFirst-party docs explicitly claim SOC 2 Type II completion and a HIPAA-compliant pipeline with BAA for Enterprise customers, plus BYOC/self-hosting and regional endpoints for data residency, directly addressing contract/medical-record processing needs. However, zero-retention handling specifically is not explicitly documented, HIPAA is gated behind 'Enterprise' tier, and there is no independent/third-party audit corroboration or hands-on confirmation of these compliance claims. Missing for 10: explicit zero-retention policy documentation, independent verification of SOC2/HIPAA claims, and clarity on whether zero-retention applies outside Enterprise tier.
- [claimed-docs] “Enterprise readiness: "LlamaParse Platform has completed a SOC 2 Type II audit. The report and subprocessor list are available through the T…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
- [claimed-docs] “LlamaParse Platform has completed a SOC 2 Type II audit. The report and subprocessor list are available through the Trust Center. A HIPAA-co…”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
- [claimed-docs] “Identity and access. Use SSO and role-based access controls to manage access to your organization and projects.”
Docs confirm SOC 2 Type 2 and HIPAA compliance plus dedicated VPC deployment with full data isolation, but no evidence explicitly describes a 'zero-retention' data handling policy for uploaded documents. missing for 10: explicit zero-retention/data-deletion policy statement, independent audit confirmation, and specifics on how contract/medical record data is purged after processing.
- [claimed-docs] “Security and compliance overview: "SOC 2 Type 2: Controls are implemented and audited for security, availability, and confidentiality. GDPR:…”
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “IP Allowlisting - restricts Unstructured platform access to specific source IP addresses or CIDR ranges. Submit a support ticket with your I…”
Deployment
data engineerRun the extraction stack in my own VPC or fully self-hosted when documents can't leave my infrastructure
weight 2 · round to LlamaParseDocs explicitly describe BYOC/self-hosted deployment of the full LlamaCloud platform (Parse, Extract) on Kubernetes via Helm charts across AWS/Azure/GCP, keeping data and infrastructure under customer control, plus enterprise deployment options including single-tenant and regional endpoints. Missing for 10: independent/hands-on verification of self-hosted deployment success and more detail on operational limitations of self-hosting vs managed SaaS.
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure... give you the full capabilities of the LlamaCloud platform while keepin…”
Docs confirm dedicated instance/VPC deployment with full data isolation is offered as a paid tier, plus IP allowlisting and SOC2/GDPR/HIPAA compliance, which supports data-residency needs. However, evidence does not describe a fully self-hosted/on-prem/air-gapped option (only 'dedicated instance or VPC' managed by vendor), and there's no detail on installation architecture, network egress requirements, or how open-source components could be run entirely offline. missing for 10: explicit self-hosted/on-prem deployment guide, air-gapped operation details, independent confirmation of VPC isolation claims.
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “IP Allowlisting - restricts Unstructured platform access to specific source IP addresses or CIDR ranges. Submit a support ticket with your I…”
- [claimed-docs] “**IP Allowlisting** - restricts Unstructured platform access to specific source IP addresses or CIDR ranges. Submit a support ticket with yo…”
- [claimed-docs] “Security and compliance overview: "SOC 2 Type 2: Controls are implemented and audited for security, availability, and confidentiality. GDPR:…”
Format coverage — stories about format coverage in this arenaFormat coverage
Stories about format coverage in this arena
Formats
developerOne API handles my whole document mix — PDF, DOCX, PPTX, XLSX, HTML, images, email — without per-format plumbing
weight 2 · round to UnstructuredDocs explicitly claim one unified API/SDK supporting 130+ file formats across categories (PDF, DOCX, PPTX, XLSX, HTML, images, email implied) via a single 'Parse' product with one API key/SDK, and examples show handling PDFs, Excel, scans, images, and forms without separate per-format code paths. Community feedback corroborates strong parsing on complex/mixed documents but focuses mainly on PDFs, and no independent evidence tests DOCX/PPTX/email specifically. Missing for 10: independent hands-on verification across the full non-PDF format set (DOCX, PPTX, XLSX, email) and explicit example code showing format-agnostic single-call usage.
- [claimed-docs] “LlamaParse supports 130+ file formats across four categories.”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [claimed-docs] “Parse Excel files and build a RAG app to answer questions about spreadsheet dat”
- [community] “I tried LlamaParse and was impressed by the result on a document with complex layout. None of the open-source parsers provided results even …”
Unstructured's core value proposition is a single API/SDK that partitions 65+ file types (PDF, DOCX, PPTX, XLSX, HTML, images, email implied within office/document formats) into a consistent JSON format, with auto-routing of partitioning strategy per page/type, callable via Python SDK or REST — exactly matching the 'one API, no per-format plumbing' story. Missing for 10: an explicit itemized list confirming email/XLSX support specifically (only referenced generically as '65+ file types') and independent third-party benchmarking of format coverage.
- [claimed-docs] “Replace DIY pipelines: Move solutions into production faster. Reduce engineering costs. Eliminate maintenance. Resilient partitioning logic …”
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “Auto evaluates each page and routes it to Fast, High Res, or VLM partitioning, balancing quality, speed, and cost.”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
Scale limits
data engineerThousand-page documents and multi-gigabyte files process reliably without timeouts or silent truncation
weight 2 · round drawnDocs mention async webhooks (avoiding polling/timeout issues) and a 'Cost Optimizer' for 'long mixed-complexity documents,' suggesting some design accommodation for large files, but there is no explicit claim, benchmark, or size/page limit documentation addressing thousand-page or multi-gigabyte files specifically, and no community evidence of large-file reliability. Missing for 10: documented size/page limits, explicit large-document benchmarks or case studies, and independent confirmation of no timeouts/truncation on very large files.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “turn on Cost Optimizer to keep costs down on long mixed-complexity documents”
Docs claim 'resilient partitioning logic and robust visibility' and job tracking that lets you 'inspect any files that failed during processing,' implying some built-in reliability at scale, but there is no explicit evidence of handling thousand-page documents or multi-gigabyte files, no timeout limits documented, and no benchmarks or case studies addressing silent truncation. Missing for 10: documented file-size/page limits, explicit large-document benchmarks, evidence of timeout handling, and independent confirmation of reliability at scale.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Replace DIY pipelines: Move solutions into production faster. Reduce engineering costs. Eliminate maintenance. Resilient partitioning logic …”
- [claimed-docs] “Auto evaluates each page and routes it to Fast, High Res, or VLM partitioning, balancing quality, speed, and cost.”
Ocr multilingual — stories about ocr multilingual in this arenaOcr multilingual
Stories about ocr multilingual in this arena
Languages
developerNon-English documents — including CJK and right-to-left scripts — parse with the same fidelity as English
weight 2 · round drawnLlamaParsenone0/10No evidence in the pack addresses multilingual or CJK/RTL parsing fidelity; docs mention layout-aware OCR, format support, and general parsing quality but nothing about language-specific handling or non-English script accuracy.
Ocr
developerHandwritten fields and annotations are recognized and extracted, flagged with confidence when uncertain
weight 1 · round to LlamaParseDocs claim handwriting recognition as part of layout-aware OCR ('turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown') and an enriched forms pass returns field values, checkbox states, and bounding boxes as structured JSON, but there is no documented confidence scoring or uncertainty flagging for handwritten fields/annotations specifically. Missing for 10: explicit confidence/uncertainty scores per extracted field, independent validation of handwriting accuracy, and any mention of flagging low-confidence handwritten extractions.
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
Unstructurednone0/10The evidence covers partitioning, chunking, table-to-HTML, and generative OCR/VLM enrichment, but nothing specifically addresses recognition of handwritten fields/annotations or confidence-flagging for uncertain extractions. This is a fair OCR-category question, but no supporting evidence exists.
developerScanned and photographed documents OCR accurately — skewed pages, stamps, low quality scans included
weight 3 · round drawnLlamaParse's docs claim strong OCR for scans/photos, complex layouts, handwriting, checkboxes and images (llamaparse-docs-25, llamaparse-docs-12, llamaparse-docs-2), and community feedback confirms it handles complex layouts better than open-source parsers (llamaparse-comm-1). However, no evidence specifically addresses skewed-page correction, stamp detection, or degraded/low-quality scan handling, and community reports flag inconsistent table extraction and an independent benchmark showing lower faithfulness than claimed (llamaparse-comm-3, llamaparse-comm-6). missing for 10: explicit skew-correction handling, stamp/seal recognition, low-quality scan benchmarks, and independent hands-on validation of OCR accuracy on such edge cases.
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “Turn PDFs, scans, or images into clean LLM-ready text”
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [community] “I tried LlamaParse and was impressed by the result on a document with complex layout. None of the open-source parsers provided results even …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
- [community] “I ran the baseline PyPDF+Naive RAG benchmark myself and got a faithfulness score of 0.980, actually higher than the 0.667 the team reported …”
Unstructured supports 'High Res' and VLM-based partitioning strategies and generative OCR enrichment, which are relevant to scanned/photographed documents, but there is no explicit evidence about handling skewed pages, stamps, or low-quality scans specifically, nor any accuracy benchmarks or independent hands-on validation. missing for 10: evidence of deskewing/rotation correction, stamp/handwriting handling, accuracy metrics on low-quality scans, and independent third-party validation of OCR quality.
- [claimed-docs] “Auto evaluates each page and routes it to Fast, High Res, or VLM partitioning, balancing quality, speed, and cost.”
- [claimed-docs] “After partitioning, you can have a vision language model (VLM) optimize the fidelity of text blocks that Unstructured initially processed du…”
- [claimed-docs] “Create a job to partition and enrich local files into AI-ready JSON with image descriptions, table HTML, named entities, and generative OCR …”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnDocs show every core capability (Parse, Extract, Classify, Split, Index) is available via Python/TS/Go/Java SDKs, CLI and REST API alongside the Web UI, and webhooks let API users get async job notifications like the UI dashboard. However, admin/enterprise features (SSO, RBAC, project/org management, Trust Center reports) are described only in UI/dashboard terms with no evidence of equivalent API endpoints, and no OpenAPI spec was discoverable (probe 404s) to confirm full parity. Missing for 10: documented API endpoints for org/SSO/RBAC management, a public OpenAPI/swagger spec, and independent confirmation that all UI-configured settings (e.g., extraction schema builder) are fully API-driven.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “Identity and access. Use SSO and role-based access controls to manage access to your organization and projects.”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
- [claimed-docs] “One API key, one SDK, and five composable products: Parse (agentic OCR), Extract (structured data), Classify, Split, and Index.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.llamaindex.ai/openapi.json, https://developers.llamaindex.ai/swagger.json, https:…”
Docs show workflows, jobs, partitioning, chunking, and enrichment can all be driven via Python SDK or REST API, and the no-code UI (Pipelines) maps to the same workflow API objects, suggesting parity. However, no explicit statement confirms 100% UI-API parity, and the OpenAPI spec is not publicly resolvable (404s), making it hard to verify full API surface coverage independently. missing for 10: explicit UI/API parity statement, public OpenAPI spec confirming full endpoint coverage, independent verification of parity claims.
- [claimed-docs] “The Unstructured Pipelines workflow designer features a no-code user interface for transforming your unstructured data into data that is rea…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.unstructured.io/openapi.json, https://docs.unstructured.io/swagger.json, https://docs.u…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to LlamaParseLlamaParse's core outputs (markdown, text, JSON) are open, portable formats by design, and BYOC/self-hosting options mean users can run the entire platform on their own infrastructure without vendor lock-in. However, there's no documented explicit 'export all account data' feature or bulk data-portability tool beyond the per-job parse outputs. missing for 10: dedicated account-wide data export/deletion tooling, migration guides for leaving the platform, independent verification of format completeness.
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure... give you the full capabilities of the LlamaCloud platform while keepin…”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
Unstructured's core output is a 'consistent JSON format' (open, standard) and users can 'download results' from processing jobs and route data to 35+ destinations, which supports data portability rather than lock-in. However, there is no explicit documentation of an account-level 'export all my data and leave' capability, bulk account data export/deletion tooling, or confirmation of full openness beyond the processed JSON outputs. Missing for 10: explicit account/data export or deletion workflow, documentation of full data portability guarantees, independent confirmation of no proprietary lock-in.
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
ai-native userRead the product's source under an open license
weight 2 · round drawnLlamaParsenone0/10The evidence shows a GitHub repo (llama_cloud_services) but it is only a client SDK/wrapper for calling the hosted LlamaParse API, not the source of the core parsing engine, and no license terms or open-source claim for the actual product are given. There is no documentation indicating LlamaParse's core service or models are released under an open license.
- [github] “Please migrate to the new packages: - **Python**: `pip install llama-cloud>=1.0`”
ai-native userSelf-host the core product
weight 3 · round to LlamaParseDocs explicitly describe self-hosting/BYOC deployments giving full LlamaCloud capabilities within customer infrastructure, including Kubernetes/Helm deployment on AWS/Azure/GCP, plus enterprise deployment options (managed SaaS, single-tenant, BYOC, self-hosting, regional endpoints). Missing for 10: independent/hands-on confirmation of a self-hosted deployment actually running (no community reports), and details on licensing/open-source availability of the self-hosted code vs. it being a gated enterprise offering.
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure... give you the full capabilities of the LlamaCloud platform while keepin…”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
Docs mention deploying Unstructured in your own dedicated instance or VPC with multi-user access and full data isolation, which implies a self-hosted deployment option, but this is framed as an enterprise/paid offering with tailored pricing and support rather than a freely self-hostable open-source core with clear installation instructions. missing for 10: no documentation of a downloadable/open-source self-host package, no setup/installation guide for running the core independently, no confirmation this is free or community-supported rather than a paid enterprise deal.
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “**IP Allowlisting** - restricts Unstructured platform access to specific source IP addresses or CIDR ranges. Submit a support ticket with yo…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
Parse accuracy — stories about parse accuracy in this arenaParse accuracy
Stories about parse accuracy in this arena
Evals
ml engineerThe vendor publishes reproducible accuracy benchmarks and I can run my own evals before committing
weight 1 · round drawnLlamaParsenone0/10The evidence pack contains no vendor-published reproducible accuracy benchmarks (docs describe features, formats, and getting-started SDK usage, but no benchmark methodology, dataset, or published accuracy numbers) and no first-party guidance on running independent evals. A community report (comm-6) even claims a self-run baseline outperformed a previously reported LlamaParse pipeline number, but this is a single community claim referencing an external benchmark, not a vendor-published reproducible benchmark suite, so it cannot establish 'disputed' status. missing for 10: vendor-published benchmark methodology/dataset, published accuracy metrics, eval harness or reference scripts for ML engineers to reproduce results, any first-party corroboration of benchmark claims.
- [community] “I ran the baseline PyPDF+Naive RAG benchmark myself and got a faithfulness score of 0.980, actually higher than the 0.667 the team reported …”
Figures
ml engineerFigures and charts are extracted or described (VLM summaries, image crops) with positions traceable back to the source page
weight 2 · round drawnDocs confirm layout-aware parsing of charts/images into markdown and table extraction with source-page provenance (docs-15, docs-22, docs-25), and a community request for page numbers alongside markdown (comm-7) suggests this is not fully solved out-of-the-box. There's no explicit evidence of VLM-generated figure/chart summaries or image crop extraction with bounding boxes tied back to page position (only forms/checkbox bounding boxes are documented). missing for 10: explicit VLM-based figure/chart description or summarization feature, documented image-crop extraction with bounding-box/page coordinates for charts/figures specifically, and independent hands-on confirmation of this traceability.
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [community] “LlamaParse looks nice. Is there a way to return page numbers also with the markdown? This is important for our use case.”
Unstructured docs confirm image/figure handling via enrichment ('image descriptions', VLM-based generative OCR, VLM-based table-to-HTML) and partitioning into structured JSON elements with metadata, supporting the VLM-summary/image-crop part of the story. However, no evidence pack item explicitly documents that extracted figures/images carry page-number or coordinate metadata that traces them back to the source page location. Missing for 10: explicit documentation of bounding-box/page-position metadata for image/figure elements, and any independent/hands-on confirmation of accurate spatial traceability.
- [claimed-docs] “After partitioning, you can have a vision language model (VLM) optimize the fidelity of text blocks that Unstructured initially processed du…”
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format. This table-to-HTML outp…”
- [claimed-docs] “Create a job to partition and enrich local files into AI-ready JSON with image descriptions, table HTML, named entities, and generative OCR …”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
Layout
developerThe API parses complex real-world PDFs — multi-column layouts, headers, footers, footnotes — into clean, correctly ordered content
weight 3 · round to UnstructuredLlamaParsedisputedcontradicted5/10Docs claim agentic, layout-aware OCR that turns complex layouts, tables, charts, and handwriting into clean markdown (llamaparse-docs-2, llamaparse-docs-25), and one HN commenter found it markedly better than open-source parsers on complex layouts (llamaparse-comm-1). But other hands-on users report concrete accuracy gaps — table data extracted but not returned in usable tabular format (llamaparse-comm-3) and a benchmark run showing LlamaParse-based pipeline faithfulness (0.667) actually lower than a naive PyPDF baseline (0.980) (llamaparse-comm-6) — directly contradicting the 'clean, correctly ordered' claim for some real-world documents. missing for 10: independent benchmark specifically on multi-column/headers/footers/footnotes ordering, resolution of the conflicting community reports, and reproducible accuracy metrics.
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [community] “I tried LlamaParse and was impressed by the result on a document with complex layout. None of the open-source parsers provided results even …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
- [community] “I ran the baseline PyPDF+Naive RAG benchmark myself and got a faithfulness score of 0.980, actually higher than the 0.667 the team reported …”
Unstructured's docs describe partitioning into structured JSON with auto-routing across Fast/High-Res/VLM strategies, table-to-HTML, and generative OCR enrichment, implying handling of complex layouts, but there is no explicit documentation or evidence addressing multi-column reading order, header/footer suppression, or footnote handling specifically, nor any independent benchmark or hands-on validation of parse accuracy on real-world PDFs. missing for 10: explicit multi-column/column-order handling documentation, header/footer/footnote-specific treatment, independent accuracy benchmarks or user testimonials confirming correct ordering.
- [claimed-docs] “Auto evaluates each page and routes it to Fast, High Res, or VLM partitioning, balancing quality, speed, and cost.”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “After partitioning, you can have a vision language model (VLM) optimize the fidelity of text blocks that Unstructured initially processed du…”
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format.”
- [claimed-docs] “To choose one of these strategies, select one of the following four **Partition Strategy** options for the **Partitioner** node of a workflo…”
ml engineerParsed output preserves document hierarchy — headings, sections, reading order — so downstream LLMs see structure, not soup
weight 2 · round drawnDocs describe LlamaParse as 'layout-aware OCR' that converts complex layouts, tables, charts, and headings into 'clean markdown,' implying structural/hierarchy preservation, and a community reviewer praised its handling of complex layouts. However, another hands-on user reported that table data wasn't returned in proper tabular structure and was only accessible via Q&A, raising doubts about how faithfully structural elements are preserved, and no evidence explicitly confirms heading-level/section hierarchy or reading-order fidelity beyond general layout claims. Missing for 10: explicit documentation/examples of heading-level and section-order preservation, and independent benchmarking confirming structural fidelity beyond tables.
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “Guide parsing output with custom prompts. Extract specific data from a McDonald's receipt by instructing the parser to focus only on prices …”
- [community] “I tried LlamaParse and was impressed by the result on a document with complex layout. None of the open-source parsers provided results even …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
Docs describe partitioning as producing structured document elements and metadata in a consistent JSON format, and chunking strategies like 'by title' imply awareness of headings/sections for logical grouping. However, there is no explicit documentation addressing reading-order preservation across multi-column or complex layouts, or how nested section hierarchy (e.g., parent/child heading relationships) is represented in output. missing for 10: explicit reading-order guarantees, documented hierarchy/nesting model for headings and sections, and independent/hands-on validation that structure survives complex layouts.
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “You can further control this behavior with by title, by page, and by similarity chunking strategies.”
- [claimed-docs] “You can further control this behavior with [by title](#chunk-by-title-strategy), [by page](#chunk-by-page-strategy), and [by similarity](#ch…”
- [claimed-docs] “To choose one of these strategies, select one of the following four **Partition Strategy** options for the **Partitioner** node of a workflo…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to LlamaParseDocs state the platform offers 'managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints' for deployment and data residency, and self-hosting/BYOC explicitly lets customers keep data and infrastructure under their own control (including choice of cloud/region via Kubernetes on AWS/Azure/GCP). However, there is no detail on which specific regions are available for the managed SaaS regional-endpoint option, no UI/API mechanism shown for selecting a region, and no independent confirmation. Missing for 10: concrete list of supported regions/endpoints, documented API/UI control to select a region, and third-party or hands-on confirmation of data residency behavior.
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
Unstructured documents dedicated-instance/VPC deployment options (full data isolation, tailored pricing) and GDPR compliance, which implies some customer control over where data resides, but there is no explicit region-selection feature, multi-region hosting options, or documentation describing how a customer chooses a specific data residency zone. Missing for 10: explicit region/residency selection UI or config, list of supported hosting regions, and independent confirmation that VPC deployment lets customers pick geographic location.
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “Security and compliance overview: "SOC 2 Type 2: Controls are implemented and audited for security, availability, and confidentiality. GDPR:…”
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnLlamaParsenone0/10The evidence covers enterprise features like SOC2/HIPAA compliance, SSO/RBAC, and self-hosting/BYOC options, but nowhere states an explicit policy or toggle for preventing customer data from being used to train AI models. Self-hosting implies data stays on the customer's infra, but that is not the same as a documented no-training-use guarantee.
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “Identity and access. Use SSO and role-based access controls to manage access to your organization and projects.”
- [claimed-docs] “Enterprise readiness: "LlamaParse Platform has completed a SOC 2 Type II audit. The report and subprocessor list are available through the T…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
Unstructurednone0/10The evidence covers data isolation, dedicated VPC deployment, IP allowlisting, and SOC2/GDPR/HIPAA compliance, but nowhere states an explicit policy on whether customer data is or isn't used to train Unstructured's or third-party AI models. Missing for 10: an explicit no-training-on-customer-data policy, an opt-out/opt-in training control, or any documentation addressing AI model training use of ingested data.
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “Security and compliance overview: "SOC 2 Type 2: Controls are implemented and audited for security, availability, and confidentiality. GDPR:…”
- [claimed-docs] “IP Allowlisting - restricts Unstructured platform access to specific source IP addresses or CIDR ranges. Submit a support ticket with your I…”
ai-native userControl data retention and deletion
weight 2 · round to UnstructuredLlamaParse offers BYOC/self-hosting so customers can keep all data under their own infrastructure control, and cites SOC2 Type II/HIPAA compliance, which implies some data governance posture, but no evidence describes an explicit data retention policy, configurable retention windows, or a deletion API/mechanism for the managed SaaS offering. missing for 10: explicit retention period documentation, a data deletion API/endpoint, and confirmation of deletion behavior for managed (non-BYOC) deployments.
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure... give you the full capabilities of the LlamaCloud platform while keepin…”
- [claimed-docs] “Enterprise readiness: "LlamaParse Platform has completed a SOC 2 Type II audit. The report and subprocessor list are available through the T…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
- [claimed-docs] “Deploy LlamaCloud in your own cloud infrastructure with full self-hosting and BYOC support. Run LlamaParse, LlamaExtract, and the complete L…”
Compliance docs claim GDPR conformance (which implies data deletion rights) and workflows can be deleted via API, plus dedicated VPC deployments offer full data isolation, but there is no explicit documentation of data retention periods, configurable deletion of processed/stored documents, or data lifecycle controls beyond deleting workflow definitions. missing for 10: explicit retention policy settings, documented data deletion/purge mechanisms for processed files, and independent verification of these claims.
- [claimed-docs] “Security and compliance overview: "SOC 2 Type 2: Controls are implemented and audited for security, availability, and confidentiality. GDPR:…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnLlamaParsenone0/10No evidence pack content addresses telemetry/usage-tracking opt-out settings for LlamaParse; only self-hosting/BYOC and enterprise compliance features (SOC2, HIPAA, SSO) are documented, none of which explicitly describe a telemetry opt-out control.
Rag chunking — stories about rag chunking in this arenaRag chunking
Stories about rag chunking in this arena
Chunking
ai-native userOutput comes pre-chunked for RAG — semantic boundaries, metadata, embedding-ready segments — not a wall of text
weight 3 · round to UnstructuredLlamaParse's Index product offers a hosted vector-search/embedding pipeline (docs-19, docs-30, docs-31) and structured JSON/table extraction with page-level provenance (docs-15, docs-22), suggesting some RAG-ready segmentation, but the evidence never documents explicit semantic chunk boundaries or embedding-ready segment metadata as a first-class output of Parse itself, and a community question about even basic page-number metadata in markdown output (llamaparse-comm-7) went unanswered, indicating gaps in chunk-level metadata support. missing for 10: explicit chunking/boundary strategy documentation, embedding-ready segment schema, confirmed page/metadata tagging in default output.
- [claimed-docs] “Build a hosted vector search pipeline for RAG”
- [claimed-docs] “If you don’t want to set up and host a vector database, we offer a full-managed option in which we host the vector database for you. Alterna…”
- [claimed-docs] “We support a variety of embedding models that you can choose from”
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
- [community] “LlamaParse looks nice. Is there a way to return page numbers also with the markdown? This is important for our use case.”
Docs directly describe chunking as a core post-partitioning step that produces embedding-sized chunks with multiple semantic strategies (by title, by page, by similarity) plus embedding generation and consistent JSON with metadata, matching the RAG-ready story. Missing for 10: independent/hands-on corroboration of chunk quality and semantic boundary accuracy beyond first-party docs.
- [claimed-docs] “After partitioning, _chunking_ rearranges the resulting document elements into manageable “chunks” to stay within the limits of an embedding…”
- [claimed-docs] “You can further control this behavior with by title, by page, and by similarity chunking strategies.”
- [claimed-docs] “You can further control this behavior with [by title](#chunk-by-title-strategy), [by page](#chunk-by-page-strategy), and [by similarity](#ch…”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “Create a job to partition, chunk, and embed local files into AI-ready JSON with vector embeddings for semantic search.”
Output
ai-native userI get clean markdown/JSON designed for LLM consumption, with noise like repeated headers and page furniture stripped
weight 2 · round to LlamaParseDocs strongly market LlamaParse as an agentic, layout-aware parser producing 'clean markdown, text, or JSON' from complex documents (docs-2, docs-12, docs-25) with markdown expansion options (docs-11), and early community feedback praised its handling of complex layouts versus open-source parsers (comm-1, comm-2). However, no evidence specifically addresses stripping of repeated headers/page furniture, and some hands-on community feedback flags real output-quality gaps (tables not returned in tabular form, disputed benchmark numbers) that temper the 'clean for LLM consumption' claim (comm-3, comm-6). Missing for 10: explicit documentation/example of header/footer/page-furniture deduplication, and independent verification of noise-free markdown output.
- [claimed-docs] “Parse is an agentic document parser built for LLM pipelines—layout-aware OCR that turns PDFs, scans, tables, and charts into clean markdown,…”
- [claimed-docs] “Turn PDFs, scans, or images into clean LLM-ready text”
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [community] “I tried LlamaParse and was impressed by the result on a document with complex layout. None of the open-source parsers provided results even …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
- [community] “I ran the baseline PyPDF+Naive RAG benchmark myself and got a faithfulness score of 0.980, actually higher than the 0.667 the team reported …”
Unstructured's docs show partitioning converts raw files into a 'predefined, consistent, expressive, and contextualized JSON format' of document elements and metadata, plus chunking strategies to prepare RAG-ready data, which supports the general goal of clean, LLM-consumable structured output (unstructured-docs-32, unstructured-docs-33, unstructured-docs-9). However, there is no explicit mention of markdown output or of specifically stripping repeated headers/footers/page furniture as the story describes. Missing for 10: explicit markdown export format, explicit documentation of header/footer/page-furniture removal logic, and independent verification of output cleanliness.
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “After partitioning, _chunking_ rearranges the resulting document elements into manageable “chunks” to stay within the limits of an embedding…”
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
Scale async — stories about scale async in this arenaScale async
Stories about scale async in this arena
Async
developerLong parses run as async jobs with status polling and completion webhooks, so my pipeline never blocks
weight 3 · round to LlamaParseDocs explicitly describe async job parsing with status polling replaceable by webhooks ('Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail, or reach other states') and the getting-started/parse job flow confirms async job submission. Missing for 10: independent/hands-on confirmation of webhook reliability at scale and detail on retry/backoff semantics for polling.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
Docs confirm job-based async processing with status tracking (trigger runs, monitor status, download results, inspect failed files) via the Job APIs, supporting non-blocking pipelines. However, there is no explicit mention of completion webhooks or callback notifications — polling appears to be the only documented mechanism. missing for 10: documented webhook/callback support on job completion, evidence of async job creation returning immediately with a job ID, and independent/hands-on confirmation of non-blocking behavior at scale.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
Latency
developerA fast synchronous mode returns results in seconds for interactive apps, with latency documented per mode
weight 2 · round drawnLlamaParsenone0/10The evidence pack shows async-style job submission with polling or webhooks (llamaparse-docs-6) and tiered parsing modes (e.g., 'agentic' tier in llamaparse-docs-11), but there is no documentation of a fast synchronous mode returning results in seconds, nor any per-mode latency figures.
Unstructurednone0/10Evidence mentions 'about 5 minutes' quickstarts and job/pipeline processing, but there is no documentation of a distinct fast synchronous processing mode with per-mode latency figures (seconds) suitable for interactive apps. missing for 10: explicit synchronous/async mode distinction, documented latency benchmarks per mode, evidence of sub-minute/seconds response times.
- [claimed-docs] “Use Unstructured with Python to go from an unstructured source file to structured data output in about 5 minutes.”
- [claimed-docs] “From login to structured JSON in about 5 minutes, with Unstructured and Python.”
- [claimed-docs] “Auto evaluates each page and routes it to Fast, High Res, or VLM partitioning, balancing quality, speed, and cost.”
Scale
data engineerI push high-volume batches — millions of pages — with documented rate limits and predictable throughput
weight 2 · round drawnLlamaParse documents async job status via webhooks (avoiding polling) and offers self-hosted/BYOC deployment for scaling infrastructure, which supports high-volume async workflows, but there is no documented rate-limit table, batch-submission API, or throughput/SLA numbers for millions-of-pages workloads. Missing for 10: explicit rate-limit documentation, batch endpoint semantics, throughput benchmarks or SLAs for large-scale ingestion.
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure. Self-hosted deployments — also known as BYOC (Bring Your Own Cloud) — gi…”
- [claimed-docs] “LlamaCloud can be deployed entirely within your own infrastructure... give you the full capabilities of the LlamaCloud platform while keepin…”
- [claimed-docs] “Enterprise readiness, deployment & data residency: "managed SaaS, single-tenant, BYOC, self-hosting, and regional endpoints" — the platform …”
Unstructured documents job/workflow APIs for tracking processing jobs, dedicated VPC instances for scale, and a 10,000 free-page tier, implying batch/production-scale capability, but no evidence pack item specifies actual rate limits, throughput numbers, or SLAs for millions of pages. missing for 10: documented rate limits (requests/sec or pages/hour), throughput benchmarks at millions-of-pages scale, and any independent corroboration of predictable performance at that volume.
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “Deploy Unstructured in your own dedicated instance or VPC with multi-user access, full data isolation, dedicated technical support, and pric…”
- [claimed-docs] “Built for teams of any size that need privacy, control, and security. Deploy Unstructured in your own dedicated instance or VPC with multi-u…”
- [claimed-docs] “Start processing your data with 10,000 free pages.”
Sdk dx — stories about sdk dx in this arenaSdk dx
Stories about sdk dx in this arena
Playground
developerI drag a document into a web playground and see parse/extract results before writing any code
weight 1 · round to LlamaParseDocs confirm a Web UI option alongside SDKs/CLI (llamaparse-docs-1) and explicitly describe dragging and dropping a document into LlamaParse to extract data (llamaparse-docs-14), and community evidence confirms an actual interface exists that users interacted with directly (llamaparse-comm-3, llamaparse-comm-4). However, evidence doesn't show a dedicated 'playground' branding, screenshots, or hands-on positive confirmation of the full parse-before-code workflow, and one community report calls the interface itself confusing. Missing for 10: explicit playground UI walkthrough/screenshots, independent hands-on confirmation of drag-and-drop parse+extract results without any code, and resolution of the UI confusion complaint.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
- [community] “Signing up for LlamaParse was rough: email signup endlessly redirected, click link in email, asked to sign up again with email, click link a…”
Unstructurednone0/10Evidence describes a no-code workflow designer and quickstart guides requiring Python/API calls, but nothing indicates a simple drag-and-drop web playground for instant parse/extract preview without writing code.
- [claimed-docs] “The Unstructured Pipelines workflow designer features a no-code user interface for transforming your unstructured data into data that is rea…”
- [claimed-docs] “This quickstart partitions an example company annual report with a sample Python script and the Unstructured API.”
- [claimed-docs] “From login to structured JSON in about 5 minutes, with Unstructured and Python.”
Sdks
developerOfficial typed SDKs for Python and TypeScript cover the full API — parse, extract, jobs — with sensible defaults
weight 3 · round to LlamaParseDocs confirm official Python and TypeScript SDKs ("whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API") and show a Python code sample for parsing with defaults (tier, version, expand), plus a webhook/job-status system, and GitHub shows an actively maintained llama-cloud Python package. However, there's no TypeScript code sample, no explicit documentation of a typed Extract or Jobs SDK surface, and no independent corroboration of SDK typing quality or defaults across both languages. Missing for 10: TypeScript SDK code examples, explicit typed Extract/Jobs API coverage in both SDKs, and third-party validation of SDK completeness.
- [claimed-docs] “Get your first parse job running in under a minute—whether you prefer Python, TypeScript, Go, Java, the CLI, the REST API, or the Web UI.”
- [claimed-docs] “result = client.parsing.parse( file_id=file.id, tier="agentic", version="latest", expand=["markdown"],)”
- [claimed-docs] “Instead of continuously polling for status updates, you can configure webhook endpoints to be notified immediately when jobs complete, fail,…”
- [github] “Please migrate to the new packages: - **Python**: `pip install llama-cloud>=1.0`”
- [claimed-docs] “LlamaExtract provides a simple API for extracting structured data from unstructured documents like PDFs, text files, and images.”
Extensive docs confirm a well-documented Python SDK covering partition, enrich, chunk, embed, and workflow/job management (unstructured-docs-4, 7, 19, 23, 30, 35, 36), but there is no evidence anywhere in the pack of an official TypeScript/JS SDK - only Python SDK and generic REST clients are mentioned. missing for 10: TypeScript SDK evidence, explicit coverage of jobs API via SDK (vs REST-only), independent developer corroboration of SDK ergonomics
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “You can call the Unstructured API with the [Unstructured Python SDK](/overview-python-sdk) and with standard [REST clients](/overview-rest-a…”
- [claimed-docs] “Build and manage Unstructured workflows with the Python SDK or REST endpoints. Create, update, run, and delete workflows that process and tr…”
- [claimed-docs] “Track and control the processing jobs that execute your workflows. Trigger runs, monitor status, download results, and inspect any files tha…”
- [claimed-docs] “You can call the Unstructured API through REST endpoints by using a REST client (such as cURL or Postman) to partition, enrich, chunk, and e…”
Structured extraction — stories about structured extraction in this arenaStructured extraction
Stories about structured extraction in this arena
Grounding
ai-native userEvery extracted field carries provenance — page number, bounding box, source snippet — so agents can cite and humans can verify
weight 2 · round to LlamaParseDocs show real provenance features—table extraction with source-page provenance, forms enrichment with bounding boxes and field values, and SEC-filing extraction with citations/verification against source—but these are scattered across specific modes (forms, tables, extract) rather than a universal guarantee that every extracted field always carries page+bbox+snippet. A community question explicitly asks whether page numbers can be returned with markdown output, suggesting this isn't uniformly available across the core Parse output. Missing for 10: a unified schema showing page number + bounding box + snippet attached to every field across all extraction modes, and independent confirmation that this works reliably in practice.
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
- [claimed-docs] “Extract structured data from SEC filings with citations. Verify values against the source document when extracting from complex financial do…”
- [community] “LlamaParse looks nice. Is there a way to return page numbers also with the markdown? This is important for our use case.”
Docs confirm partitioning outputs 'document elements and metadata' in structured JSON (docs-32) and structured extraction into custom JSON fields (docs-26, docs-34), which implies some per-element metadata, but the evidence pack never explicitly documents page number, bounding box, or source-snippet fields as part of that metadata, nor any citation/verification workflow for agents or humans. missing for 10: explicit documentation of page-number/bounding-box/source-snippet fields in the metadata schema, examples of extracted fields carrying provenance, and any human/agent verification or citation workflow.
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “It lets you define the target structure up front. Unstructured then extracts values in a consistent JSON format that matches your fields, re…”
- [claimed-docs] “Learn how Unstructured’s structured data extractor turns partitioned documents into custom defined JSON fields instead of generic text eleme…”
Review
data engineerExtractions carry calibrated confidence scores with a human-in-the-loop review path for low-confidence fields
weight 2 · round drawnLlamaParsenone0/10No evidence of calibrated confidence scores per extracted field or any human-in-the-loop review workflow for low-confidence extractions. Docs mention citation/verification against source documents (llamaparse-docs-32) and bounding boxes for form fields (llamaparse-docs-22), but nothing about confidence scoring or a review queue/UI for flagged low-confidence fields.
- [claimed-docs] “Extract structured data from SEC filings with citations. Verify values against the source document when extracting from complex financial do…”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
Unstructurednone0/10The evidence describes JSON schema extraction, partitioning, chunking, and enrichment, but nowhere mentions confidence scores on extracted fields nor any human-in-the-loop review workflow for low-confidence outputs. Job monitoring/failure inspection (unstructured-docs-5) covers pipeline failures, not per-field confidence-based review.
Schemas
developerI supply a JSON schema and get back validated structured fields extracted from the document
weight 3 · round to UnstructuredLlamaExtract (part of LlamaParse/LlamaCloud) explicitly supports defining an extraction schema/configuration and returning structured JSON matching that schema, including SEC filings extraction with citations and prompt-based schema generation. This directly matches the story, but evidence is entirely first-party docs with no independent/hands-on corroboration of schema validation accuracy for LlamaExtract specifically. Missing for 10: independent/community validation of extraction accuracy against schemas, explicit detail on validation/error-handling mechanics.
- [claimed-docs] “LlamaExtract provides a simple API for extracting structured data from unstructured documents like PDFs, text files, and images.”
- [claimed-docs] “Pull structured JSON out of documents that matches my schema”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
- [claimed-docs] “Extract structured data from SEC filings with citations. Verify values against the source document when extracting from complex financial do…”
- [claimed-docs] “Generate extraction schemas with a prompt”
Docs explicitly describe a structured data extractor where developers define a target JSON schema up front and Unstructured extracts values into matching fields in consistent JSON format (docs-3, docs-26, docs-34), backed by API/SDK access to run this (docs-4, docs-23). Missing for 10: independent/hands-on validation of extraction accuracy and no direct example showing schema validation errors or edge-case handling.
- [claimed-docs] “Define your own target JSON schema and have Unstructured extract values from your source files and data records directly into that shape in …”
- [claimed-docs] “It lets you define the target structure up front. Unstructured then extracts values in a consistent JSON format that matches your fields, re…”
- [claimed-docs] “Learn how Unstructured’s structured data extractor turns partitioned documents into custom defined JSON fields instead of generic text eleme…”
- [claimed-docs] “You can call the Unstructured API with the Unstructured Python SDK and with standard REST clients (such as cURL and Postman).”
- [claimed-docs] “The Unstructured Python SDK enables you to call the Unstructured API with standard Python code to partition, enrich, chunk, and embed your f…”
Splitting
data engineerMulti-document packets are classified and split automatically — one upload, per-document results
weight 2 · round to LlamaParseLlamaParse's Split API explicitly segments concatenated PDFs into logical document sections based on content categories, and Classify auto-categorizes documents by type, together enabling one-upload, multi-document packet handling with per-document results (llamaparse-docs-5, llamaparse-docs-4, llamaparse-docs-37, llamaparse-docs-38). Missing for 10: independent/hands-on validation of the Split+Classify combined workflow at scale and confirmation of per-document output structure/ordering beyond docs examples.
- [claimed-docs] “The Split API provides a simple way to automatically segment concatenated PDFs into logical document sections based on content categories.”
- [claimed-docs] “Classify lets you automatically categorize documents into types you define (for example: invoice, receipt, contract) using natural-language …”
- [claimed-docs] “Split a PDF containing multiple documents (essays, research papers) into separate segments using AI-powered classification.”
- [claimed-docs] “Classify documents from the CUAD dataset as co-branding contracts or affiliate agreements.”
- [claimed-docs] “Save reusable classification rules as a configuration and reference them by ID across multiple jobs.”
Unstructurednone0/10Evidence covers partitioning, chunking, enrichment, and structured JSON extraction, but nothing describes detecting multiple distinct documents within a single uploaded file/packet, classifying each, and returning separate per-document results. Missing for 10: any mention of packet/document splitting, document-boundary detection, or classification of sub-documents within one upload.
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
- [claimed-docs] “To choose one of these strategies, select one of the following four **Partition Strategy** options for the **Partitioner** node of a workflo…”
- [claimed-docs] “You can further control this behavior with by title, by page, and by similarity chunking strategies.”
Table extraction — stories about table extraction in this arenaTable extraction
Stories about table extraction in this arena
Tables
data engineerComplex tables — merged cells, nested headers, multi-page spans — come out as faithful HTML/markdown structure
weight 3 · round to UnstructuredLlamaParsedisputedcontradicted5/10LlamaParse docs claim to turn 'complex layouts, tables' into clean markdown and to pull tables into structured formats with page provenance, but a hands-on community report says the tool 'can extract numbers in tables, but the output isn't provided in tabular format—access to the numbers is only available through question-answering,' directly contradicting the claim of faithful structured table output. No evidence specifically addresses merged cells, nested headers, or multi-page spans in either direction. missing for 10: explicit documentation/testing of merged-cell, nested-header, and multi-page table handling, and independent corroboration resolving the contradiction.
- [claimed-docs] “Turn even the most complex layouts, tables, charts, handwriting, checkboxes, and images into clean markdown”
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Turn on the enriched forms pass to get each form page as structured JSON — fields with values, checkbox states, and bounding boxes — and rea…”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
Unstructured documents a table-to-HTML enrichment feature that converts detected tables into HTML markup using agentic AI or a VLM, which is directly relevant to table structure fidelity, but no evidence addresses handling of merged cells, nested headers, or tables spanning multiple pages — the specific complex-table scenarios in the story are unaddressed. missing for 10: evidence of merged-cell handling, nested header preservation, multi-page table stitching, and any accuracy benchmarks or independent validation of table fidelity.
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format.”
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format. This table-to-HTML outp…”
data engineerI turn extracted tables into typed rows/JSON I can load into a database without manual cleanup
weight 2 · round to UnstructuredLlamaParsedisputedcontradicted5/10Docs claim strong support for turning tables into structured JSON/DataFrames with schemas (LlamaExtract's schema-based extraction, 'pull every table into pandas DataFrames with source-page provenance', 'table row extraction') that would fit a data-engineer's typed-row/JSON pipeline, but hands-on community feedback contradicts this: a user reports 'it can extract numbers in tables, but the output isn't provided in tabular format—access to the numbers is only available through question-answering,' suggesting real-world table extraction fell short of clean, database-ready structure. missing for 10: recent independent verification that schema-driven table extraction yields clean typed rows without manual cleanup, and resolution of the tabular-output complaint.
- [claimed-docs] “pull every table out into pandas DataFrames with source-page provenance, and turn on Cost Optimizer to keep costs down on long mixed-complex…”
- [claimed-docs] “Pull structured JSON out of documents that matches my schema”
- [claimed-docs] “Extract repeating entities from documents using table row extraction”
- [claimed-docs] “LlamaExtract provides a simple API for extracting structured data from unstructured documents like PDFs, text files, and images.”
- [claimed-docs] “Just define your Extraction Configuration (schema and settings), drag and drop any supported document into LlamaParse and extract data from …”
- [community] “I found the LlamaParse interface a bit confusing. It can extract numbers in tables, but the output isn't provided in tabular format—access t…”
Unstructured's docs show two relevant capabilities: table detection with HTML output (unstructured-docs-12/27) and a structured data extractor that lets users define a target JSON schema so extracted values map directly to typed fields (unstructured-docs-3/26/34), plus a general 'consistent JSON format' output (unstructured-docs-9/29/32). This supports turning extracted tables into structured JSON, but there's no worked example specifically converting table content into typed rows/records ready for DB loading, and table output defaults to HTML markup rather than row-level JSON unless combined with the separate schema extractor. missing for 10: an explicit end-to-end example/tutorial mapping detected tables to typed row/JSON output for DB ingestion, and independent/hands-on confirmation that this pipeline avoids manual cleanup.
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format.”
- [claimed-docs] “After partitioning, you can have Unstructured generate representations of each detected table in HTML markup format. This table-to-HTML outp…”
- [claimed-docs] “Define your own target JSON schema and have Unstructured extract values from your source files and data records directly into that shape in …”
- [claimed-docs] “It lets you define the target structure up front. Unstructured then extracts values in a consistent JSON format that matches your fields, re…”
- [claimed-docs] “Learn how Unstructured’s structured data extractor turns partitioned documents into custom defined JSON fields instead of generic text eleme…”
- [claimed-docs] “Unify data silos: Discover hidden insights with 35+ connectors and 65+ file types. Consistent JSON format. All-in-one data layer.”
- [claimed-docs] “_Partitioning_ converts content from unstructured files and semi-structured data records into structured [document elements and metadata](/c…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableLlamaParsen/aLlamaParse is a document-parsing/extraction service that exposes its own capabilities as an MCP server (mcp.llamaindex.ai/mcp) for other agents to call; it is not itself an agent host that plugs in and orchestrates external MCP servers' tools. The evidence pack shows only the server-provider role (docs-8, docs-16, docs-21, docs-27, probe-4), which is the wrong axis for this story.
Unstructurednone0/10Evidence shows Unstructured exposes its own Transform MCP server so external AI tools (Claude Code, Cursor, etc.) can call Unstructured's tools — this is Unstructured acting as an MCP server/provider, not as an MCP client that plugs in and uses other servers' tools. No evidence describes Unstructured consuming external MCP servers.
- [claimed-docs] “The Transform MCP server enables you to link your AI tools to Transform. You can then use your AI tools to have Transform ingest your local …”
- [claimed-docs] “This includes most AI code editors, IDEs, desktop assistants, and coding-agent frameworks. Tools such as the Codex CLI, Claude Code, Visual …”