LlamaParse
LlamaParse is an enterprise document parsing and AI pipeline platform from LlamaIndex that converts complex PDFs, Office files, and 130+ document formats into LLM-ready structured outputs. The platform offers six composable products under a single API key: Parse (agentic OCR), Extract (structured data extraction), Classify, Split, Sheets, and Index. Parse supports tier-based processing from fast and cost-effective modes to advanced agentic and agentic-plus tiers that preserve tables, figures, and layout for high-fidelity RAG and document AI workflows. Developers access the platform through Python and TypeScript SDKs or directly via the LlamaCloud REST API, with EU-region hosting available.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles LlamaParse the way a machine reads it — 59 machine-readable artifacts across 36 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — LlamaParse scores 60.5/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile LlamaParse
Each block below is one kind of artifact we hold for LlamaParse. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 36
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
LlamaParse Extract API
Structured data extraction API that pulls typed JSON output from unstructured documents using developer-defined schemas. Supports cost-effective and agentic tiers; composable wi...
LlamaParse Classify API
Document classification API that categorizes uploaded files by type or content. Available in fast (1 credit/page) and multimodal (2 credits/page) modes; useful for pre-filtering...
LlamaCloud Index API
Managed vector index API for ingesting parsed documents into searchable LlamaCloud indexes. Supports standard (1 credit/page), spreadsheet (2 credits/page), and multi-modal (2 c...
LlamaParse Agent Data API
The Agent Data API from LlamaParse — 5 operation(s) for agent data.
LlamaParse Batch Processing API
The Batch Processing API from LlamaParse — 5 operation(s) for batch processing.
LlamaParse Batches API
The Batches API from LlamaParse — 2 operation(s) for batches.
LlamaParse Beta API
The Beta API from LlamaParse — 32 operation(s) for beta.
LlamaParse Chat API
The Chat API from LlamaParse — 4 operation(s) for chat.
LlamaParse Classifier API
The Classifier API from LlamaParse — 3 operation(s) for classifier.
LlamaParse Classify API
The Classify API from LlamaParse — 3 operation(s) for classify.
LlamaParse Configurations API
The Configurations API from LlamaParse — 2 operation(s) for configurations.
LlamaParse Data Sinks API
The Data Sinks API from LlamaParse — 2 operation(s) for data sinks.
LlamaParse Data Sources API
The Data Sources API from LlamaParse — 2 operation(s) for data sources.
LlamaParse Directories API
The Directories API from LlamaParse — 2 operation(s) for directories.
LlamaParse Directory Files API
The Directory Files API from LlamaParse — 4 operation(s) for directory files.
LlamaParse Embedding Model Configs API
The Embedding Model Configs API from LlamaParse — 2 operation(s) for embedding model configs.
LlamaParse Extract API
The Extract API from LlamaParse — 5 operation(s) for extract.
LlamaParse Files API
The Files API from LlamaParse — 4 operation(s) for files.
LlamaParse Indexes API
The Indexes API from LlamaParse — 3 operation(s) for indexes.
LlamaParse Job Dashboard API
The Job Dashboard API from LlamaParse — 1 operation(s) for job dashboard.
LlamaParse LlamaExtract API
The LlamaExtract API from LlamaParse — 16 operation(s) for llamaextract.
LlamaParse Organizations API
The Organizations API from LlamaParse — 4 operation(s) for organizations.
LlamaParse Page Figures API
The Page Figures API from LlamaParse — 4 operation(s) for page figures.
LlamaParse Page Screenshots API
The Page Screenshots API from LlamaParse — 3 operation(s) for page screenshots.
LlamaParse Parse API
The Parse API from LlamaParse — 5 operation(s) for parse.
LlamaParse Parsing API
The Parsing API from LlamaParse — 14 operation(s) for parsing.
LlamaParse Pipeline Data Sources API
The Pipeline Data Sources API from LlamaParse — 4 operation(s) for pipeline data sources.
LlamaParse Pipeline Files API
The Pipeline Files API from LlamaParse — 7 operation(s) for pipeline files.
LlamaParse Pipelines API
The Pipelines API from LlamaParse — 16 operation(s) for pipelines.
LlamaParse Projects API
The Projects API from LlamaParse — 4 operation(s) for projects.
LlamaParse Retrieval API
The Retrieval API from LlamaParse — 4 operation(s) for retrieval.
LlamaParse Retrievers API
The Retrievers API from LlamaParse — 4 operation(s) for retrievers.
LlamaParse Sheets API
The Sheets API from LlamaParse — 3 operation(s) for sheets.
LlamaParse Split API
The Split API from LlamaParse — 2 operation(s) for split.
LlamaParse Usage Metrics API
The Usage Metrics API from LlamaParse — 1 operation(s) for usage metrics.
LlamaParse V2 API
The V2 API from LlamaParse — 19 operation(s) for v2.
Scroll within the panel for all 36 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Llamaparse Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Llamaparse Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Llamaparse Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
LlamaParse API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
BatchJobCreateRequest
JSON SCHEMABatchJobResponse
JSON SCHEMABody_upload_file_api_v1_parsing_upload_post
JSON SCHEMAClassifyJob
JSON SCHEMAClassifyJobCreate
JSON SCHEMAClassifyJobResults
JSON SCHEMAExtractJob
JSON SCHEMAExtractJobCreate
JSON SCHEMAExtractResultset
JSON SCHEMASplitCreateRequest
JSON SCHEMASplitJobResponse
JSON SCHEMASplitResultResponse
JSON SCHEMAScroll within the panel for all 12 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for LlamaParse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/llamaparse · machine-readable index on apis.io