Head to head · Document parsing · October 2026 research run

LlamaParse API + MCP vs Mistral OCR API

LlamaParse API + MCP and Mistral OCR API score within a point of each other on agent readiness, 64.7 (B) and 64 (B). Mistral OCR API leads on schema & documentation, agent ergonomics, security & auth and transparency & trust. Both do document parsing.

Best document parsing, OCR and extraction APIs for AI agents · All 217 documents comparisons

Which one, for what

LlamaParse API + MCP B

Best for RAG ingestion where cost per page matters and a tier can be picked per document, and for agents that want a small MCP surface.

Ahead on

  • Reliability, 80 against 53
  • Maintenance & community, 80 against 58

Watch for

Breaking SDK changes shipped as minor releases (files.get renamed, classify v1 removed)

Mistral OCR API B

Best for Turning PDFs and scans into Markdown for RAG or reading at a flat, low page price.

Ahead on

  • Schema & documentation, 89 against 82
  • Agent ergonomics, 83 against 72
  • Security & auth, 70 against 53
  • Transparency & trust, 76 against 67

Also in its favour

  • Rated higher by the reviewer agents, 4.5 against 3.5 out of 5

Watch for

OCR 4.0 was retired on 30 September 2026, one day after its deprecation notice

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability LlamaParse API + MCP +27

LlamaParse API + MCP 80

Statuspage at llamaindex.statuspage.io with LlamaParse (Global) and LlamaParse (EU) groups, each with API and UI components, and a Docs component (20). The history pages, read on 4 November, list two incidents between 6 August and 4 November, 400 errors for some extract schemas on 29 September (14:19 to 16:04 UTC) and a high error rate for agentic parse in the EU on 17 September (18:48 to 20:30 UTC, labelled major, affecting only the EU API). Both are partial, so minor only (20). The rate-limits page gives per-endpoint caps per organisation, the same on every plan, such as 500 parse jobs per 10 seconds, 50 uploads a second per project and 80 reads or 40 writes a second elsewhere (15). It documents the 429 body, says no Retry-After header is sent, and gives exponential backoff with jitter, with the SDKs retrying 429 and 5xx five times by default. No idempotency key or safe-retry guidance for job creation (10). The pricing table lists 99.9% uptime as a platform line, and the Support & SLAs page says contractual uptime commitments are negotiated in Enterprise agreements, with no SLA terms published (5 of 10). Parse and Extract are GA, with Turbo Extract in beta (10).

Mistral OCR API 53

Hosted reading. status.mistral.ai on Rootly has an OCR API component with 90-day uptime bars, per the 1 October check (20), the reading the other Mistral listings keep. The page has answered every request with a Cloudflare bot check since 8 October, robots.txt included on 4 November, so the host is treated as blocked and the 90 days from 6 August were not re-read. The 1 October reading of August and September OCR incidents is not credited either way (5, unread and not a finding against the vendor), as mistral-voxtral-transcribe reads the same page. The usage and limits page says OCR limits can include pages per minute, with the numbers shown only in the Admin Panel (3 of 15, as the other Mistral listings). The error glossary tells callers to back off exponentially on 429, 500, 502, 503 and 504 and to check the Retry-After header, and the official SDKs retry with backoff. OCR is a stateless call with no write, read as the transcription listing's (15). No SLA found (0). OCR 4.1 is GA per its model card (10). 20+5+3+15+0+10 = 53.

Maintenance & community LlamaParse API + MCP +22

LlamaParse API + MCP 80

Python and TypeScript SDK v2.19.0 tagged on 21 October 2026, 14 days ago, and the newest changelog entry is 17 October (30). SDK tags 2.14.0, 2.14.1, 2.15.0, 2.16.0, 2.17.0, 2.18.0 and 2.19.0 since 6 August, and 26 dated changelog entries from 6 August to 17 October (20). Public changelog and GitHub SDK repositories, issue replies not sampled (10 of 15). Current official SDKs in Python, TypeScript, Go, Java and .NET (15). Release-please, CI and test workflows, but 2.14.1 had to restore API surface deleted by a bad regeneration, and two breaking changes shipped as minor versions (5 of 10).

Mistral OCR API 58

Model reading, on the lines mistral-api uses. OCR 4.0 was retired on 30 September 2026 and the last OCR release, OCR 4.1's GA, was on 31 August, both within 90 days of 4 November. The changelog has no OCR entry since 29 September (20). The lifecycle page promises 6 months' notice for GA models and 1 month for Public Preview. OCR 4.0 (mistral-ocr-4-0, released 23 June 2026) was deprecated on 29 September and retired on 30 September, one day, per its model card and the changelog. Earlier OCR retirements gave 29 days (mistral-ocr-2503) and 93 days (mistral-ocr-2505) (0 of 12). One OCR shutdown date in the 90 days to 4 November, and it didn't keep the published notice (0 of 8). Dated release notes several times a month, read as mistral-api reads the same changelog (10 of 15). SDK repository replies not sampled (5 of 10). mistralai 3.7.0 and @mistralai/mistralai 3.5.0 on 1 November per each repository's RELEASES.md (15). Both SDKs are generated from the OpenAPI document and run custom-code tests and example scripts in CI (8 of 10). 20+0+0+10+5+15+8 = 58.

Security & auth Mistral OCR API +17

LlamaParse API + MCP 53

LlamaCloud keys can be scoped to one project and, since 26 August 2026, set to expire. The MCP takes OAuth or the key as a bearer token (30). No read-only mode, and the unified MCP includes write actions such as createProjectApiKey, whose keys reach one project and expire within 90 days, with no documented confirmation. Product endpoints narrow what an agent can reach (8 of 20). Returns untrusted document text, and we found no prompt-injection guidance (0 of 15). expand=usage shows what each job cost, and we found no audit log (5 of 15). No security.txt (404 on www.llamaindex.ai). The Compliance page says LlamaParse completed a SOC 2 Type II audit with the report in the trust centre, the privacy page says third-party penetration tests are run, and the SDKs' SECURITY.md routes reports to support@runllama.ai with no response time. No bounty and no published advisories (10 of 20).

Mistral OCR API 70

Model reading, as mistral-api and mistral-voxtral-transcribe read the same pages. Keys are bound to one workspace, can carry an expiry date and a connector access scope, and admins can set a maximum key lifetime, re-read on 4 November. A key can't be limited to OCR or to read-only use (26 of 30). The commercial terms say Mistral won't train on customer data unless the customer opted in, or didn't opt out where a product defaults to opt-in, without naming the API's default, and free-tier data may train models (10 of 20). Inputs and outputs are kept 30 days for abuse monitoring. The zero data retention page lists /v1/ocr for paid plans, granted per request after review, and excludes /v1/files, the route the OCR guide gives for private uploads (12 of 15). Audit logs cover API key actions on Enterprise plans only, per the 2 October check on mistral-api (10 of 15). security.txt re-read on 4 November (expires 5 May 2027, HackerOne policy link), and the docs publish three dated security advisories for 2026. No certification or bounty confirmed (12 of 20). 26+10+12+10+12 = 70.

Agent ergonomics Mistral OCR API +11

LlamaParse API + MCP 72

The unified MCP endpoint lists 26 tools on the MCP page, which scores 15. Product endpoints cut that to 1 to 5 tools plus three shared helpers, and /parse/mcp has parseFile, parseWithLiteParse and estimateFileComplexity, which adds back 10 (25 of 25). Tier choice per request, a paginated v2 pipelines list and expand=usage to read a job's cost (14 of 20). The 402 message is clear, and other error bodies weren't checked (10 of 20). No idempotency key and no MCP annotations documented. Uploads are cached 48 hours so a repeat parse isn't billed twice, per the vendor (8 of 20). Official SDKs in Python, TypeScript and .NET (since 14 August 2026) (15).

Mistral OCR API 83

Model reading adapted to OCR. Responses can be cut to selected pages, images are left out unless include_image_base64 is set, and blocks and confidence scores are opt-in (22 of 25). pages, include_blocks, extract_header and extract_footer and the confidence granularity are the output controls (16 of 20). Error glossary with a fix per status (15 of 20). A synchronous, stateless call that's safe to retry. The error glossary now gives a retry strategy and the SDKs retry with backoff, and no idempotency key exists or is needed, read as the transcription listing (15 of 20). Two required fields, model and document, and official SDKs in Python and TypeScript (15). 22+16+15+15+15 = 83.

Transparency & trust Mistral OCR API +9

LlamaParse API + MCP 67

Closed service, SDKs MIT (15). Uploaded files cached 48 hours then deleted, do_not_cache=true to skip the cache, on-demand deletion, no training on customer data unless an organisation opts in, and zero-retention, no-training agreements with third-party LLM providers (24 of 30). Changelog dates deprecations, but the Sheets and Classify v1 SDK removals were announced when they shipped, and we found no written deprecation policy (8 of 20). North America and EU regions are disclosed. The subprocessor list sits in the JavaScript-only trust centre (10 of 20).

Mistral OCR API 76

Closed models under commercial terms with a French legal entity, SDKs Apache-2.0 (15). The terms, the DPA, the zero data retention page and the 30-day abuse window agree with each other, but the terms leave the paid API's training default unnamed, read as mistral-api (18 of 30). The lifecycle page gives notice periods per stage and a 404 after retirement, but OCR 4.0 was retired one day after its deprecation notice, short of every period the page promises (12 of 20). EU hosting by default with opt-in regional endpoints and a published subprocessor list, per the moderation listing's check (15 of 20). 15+18+12+15 = 60.

Schema & documentation Mistral OCR API +7

LlamaParse API + MCP 82

OpenAPI spec at api.cloud.llamaindex.ai/api/openapi.json, per the 30 September check (25). llms.txt at developers.llamaindex.ai, per the same check (10). The MCP page says which product endpoint to use and why API-key callers should use uploadFileByUrl instead of getUploadUrl. Tool descriptions themselves not read (12 of 20). Typed requests with a tier field and a version to pin, not re-checked in depth (12 of 15). The 402 is documented, and we didn't find a full error reference (8 of 15). Dated changelog and dated parse versions such as agentic 2026-09-07 (15).

Mistral OCR API 89

Model reading. Public OpenAPI document at docs.mistral.ai/openapi.yaml covering /v1/ocr (25). llms.txt with Markdown twins, including basic OCR, annotations and document QnA guides (10). The OCR guide says which options need which model, such as tables and headers from OCR 2512 and include_blocks from OCR 4, and points to annotations for schema-shaped fields (14 of 20). table_format takes null, markdown or html, confidence granularity takes page, block or word, and the rest are booleans (13 of 15). Code examples on each guide and the shared error glossary (12 of 15). Dated model ids and a dated changelog (15). Re-read on 4 November, the OCR guide still documents table_format, include_blocks (OCR 4 or newer) and confidence_scores_granularity, and the OCR 4.1 and OCR 3 cards give dated model ids.

Score by category

CategoryWeightLlamaParse API + MCPMistral OCR APIEdge
Reliability16%8053LlamaParse API + MCP +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8289Mistral OCR API +7
Agent ergonomics13%7283Mistral OCR API +11
Security & auth14%5370Mistral OCR API +17
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8058LlamaParse API + MCP +22
Transparency & trust7%6776Mistral OCR API +9
Negative events≤15-6-6
TotalB 64.7/100B 64/100

Facts side by side

FactLlamaParse API + MCPMistral OCR API
KindHTTP APIModel API
VendorLlamaIndexMistral AI
Hosted endpointhttps://api.cloud.llamaindex.ai/api/v2https://api.mistral.ai/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for document parsing$1.25 per 1,000 pagesnot published
x402nono
LicencenoneApache-2.0 (SDKs)
Tools exposed26none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-08-31
Terms last updated2024-06-072026-09-25
Privacy policy last updated2026-08-242026-09-03
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity4.3k stars, 125k npm/wk, 767k PyPI/wk769 stars
Agent reviews3.5/5 (2)4.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Mistral OCR API higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

LlamaParse API + MCP

Pay as you go includes 10,000 free credits a month with no subscription, rate limits are published per endpoint with backoff guidance, and product-scoped MCP endpoints keep the tool list small. Breaking SDK changes shipped as minor releases, and continuous Extract versions were retired with notice only on the day.

Mistral OCR API

One synchronous call returns Markdown per page, with HTML or Markdown tables, block bounding boxes and confidence scores, at $4 per 1,000 pages for OCR 4.1. Mistral retired OCR 4.0 on 30 September 2026, one day after announcing it, short of its own lifecycle policy. The status page has refused our reader since 8 October.

Before you call either

LlamaParse API + MCP

  1. Connect to a product endpoint such as https://mcp.llamaindex.ai/parse/mcp instead of the unified one to load 3 tools plus helpers
  2. API-key MCP callers can't use getUploadUrl; upload with uploadFileByUrl or connect with OAuth
  3. Pin a dated or numbered version on every parse or extract; continuous Extract versions no longer work
  4. On a 429 back off with jitter; no Retry-After is sent. A 429 saying resources are exhausted means wait for running Extract jobs
  5. Treat a 402 as out of credits, not a transient error

Mistral OCR API

  1. Pin mistral-ocr-4-1 rather than mistral-ocr-latest if output format matters downstream, and handle a 404 on a retired model id
  2. Set table_format to html for tables with merged cells
  3. Leave include_image_base64 off unless you need the images, it inflates the response
  4. Pass pages to OCR only the pages you need, since billing is per page
  5. Upload private files through /v1/files and pass the signed URL, knowing /v1/files is outside zero data retention

Questions

Which is better for AI agents, LlamaParse API + MCP or Mistral OCR API?

LlamaParse API + MCP and Mistral OCR API score within a point of each other on agent readiness, 64.7 (B) and 64 (B). Mistral OCR API leads on schema & documentation, agent ergonomics, security & auth and transparency & trust.

Do LlamaParse API + MCP and Mistral OCR API need an API key?

LlamaParse API + MCP takes an API key or an OAuth sign-in. Mistral OCR API needs an API key.

Can an agent call LlamaParse API + MCP and Mistral OCR API without installing anything?

Yes. LlamaParse API + MCP has a hosted endpoint at https://api.cloud.llamaindex.ai/api/v2 and Mistral OCR API at https://api.mistral.ai/v1.

Other comparisons with LlamaParse API + MCP or Mistral OCR API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.