Head to head · OCR · October 2026 research run

Unstructured API + MCP vs Veryfi API + MCP

Veryfi API + MCP scores 60.6 (C) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 3 of 7 scored categories. Unstructured API + MCP leads on maintenance & community. Both do ocr.

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

Which one, for what

Unstructured API + MCP E

Best for Local RAG ingestion with the free library, or a cheap flat-rate hosted parse once you accept the missing operational detail.

Ahead on

  • Maintenance & community, 80 against 68

Also in its favour

  • Open source

Watch for

No status page, no published rate limits and no SLA

Veryfi API + MCP C

Best for Expense, accounts-payable and lending flows that need line items from receipts, invoices and bank statements at a per-document price.

Ahead on

  • Reliability, 70 against 27
  • Agent ergonomics, 75 against 58

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Unstructured API + MCP loses 6 points for them

Watch for

API down for 9 minutes on 29 September and incomplete extraction for a large portion of requests on 1 October 2026

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 Veryfi API + MCP +43

Unstructured API + MCP 27

Readings on the docs and pricing pages are per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). No status page found, status.unstructured.io didn't resolve (0). No incident history to read (5). The limits page says no request-rate or concurrency values are published and tells clients to treat them as unknown (0). The recovery guide maps rate_limited to 429, says to back off and wait for Retry-After when it's sent, and says to check existing job IDs before resubmitting, safe-retry guidance with no idempotency key (12 of 15). No SLA found (0). Transform wasn't labelled beta in the pages read (10). 0+5+0+12+0+10 = 27.

Veryfi API + MCP 70

Better Stack status page at status.veryfi.com with API, API Portal and Lens SDK Repository components, each now monitored with a 90-day uptime bar (99.984, 100 and 99.957 per cent on 4 November) and linked incidents (20). The bars cover 7 August to 4 November, so 6 August is unread. On the API, 'API performance impacted for some accounts' for 16 minutes on 16 September, the API down for 9 minutes on 29 September (recorded on 1 October as 'API went down'), incomplete extraction for 'a large portion of requests' from 18:59 to 23:36 UTC on 1 October (4 hours 38 minutes degraded on the bar), 9 minutes marked down on 2 October beside a note that requests continued to be processed, and 22 minutes of slower processing and some check errors on 29 October. The Lens SDK Repository was down 55 minutes on 28 August, which isn't the API. Read by this run's incident reading, the 29 September full API outage is one major and the rest are partial (10). Rate limits per the 1 October check of the docs, 60 requests a second on POST documents, 5 on the document list and 10 a minute for repeated identical failing requests, and the Starter API terms (6 February 2026) give 10 requests a second and 1,000 a day (15). 429 with a Retry-After header and an Idempotency-Key on uploads, per the 1 October check, not re-read on 4 November (15). SLA options on Growth and Enterprise and a 99.9 per cent uptime aim in the terms, no SLA document (0). GA (10). Total 70.

Agent ergonomics Veryfi API + MCP +17

Unstructured API + MCP 58

All readings per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). The MCP tool count isn't published. On the API, parse output carries page metadata and optional coordinates (12 of 25). jobsList, jobsGet, cancel and delete endpoints (12 of 20). Every error code has a recovery action (18 of 20). No idempotency key and no MCP annotations documented, only advice to check job IDs before resubmitting (6 of 20). Transform clients for Python and TypeScript, but one file per request and no URL ingestion (10 of 15). 12+12+18+6+10 = 58.

Veryfi API + MCP 75

The MCP server has one tool, and API responses grow only when you ask for bounding boxes or confidence details (20 of 25). max_pages_to_process, boost_mode, opt-in bounding boxes and confidence, and a paged document list (14 of 20). Twelve documented errors with a meaning each (14 of 20). Idempotency-Key on uploads per the 30 September check, and no annotations on the MCP tool (12 of 20). One required input, a file or URL, and SDKs in Python and Node.js among others (15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.

Maintenance & community Unstructured API + MCP +12

Unstructured API + MCP 80

The open-source library, a listed package, was tagged 0.27.36 on 29 October 2026, 7 days before this check (30). It has 19 tags in the 90 days from 7 August, from 0.27.0 (21 August) to 0.27.36 (20). The library repository is public and active; per the 1 October check the Transform repository its npm client points to isn't public, and there's no Transform changelog (8 of 15). Transform clients for Python and TypeScript, per the 1 October check (15). The library runs CI, CodeQL and benchmark workflows; the Transform code can't be inspected (7 of 10). 30+20+8+15+7 = 80.

Veryfi API + MCP 68

Node.js SDK v1.5.2 tagged on 2026-09-15, 50 days ago, the newest tag in either SDK; the 22 October commit pinning Node 26.12.1 is untagged (20). In the 90 days from 6 August, v1.5.0 (20 August, new API operations), v1.5.0.1 (21 August, publishing scripts only, half), v1.5.1 (25 August, test dependencies moved, half) and v1.5.2 (15 September, axios swapped for native fetch), so 3 (20). No public changelog, and the MCP server's last commit was 2025-09-26. Issue replies not sampled (5 of 15). Python SDK 5.1.0 (13 May 2026) and Node.js 1.5.2 are current (15). Both SDK repositories run test workflows. The MCP server has tests but no CI (8 of 10). Total 68.

Score by category

CategoryWeightUnstructured API + MCPVeryfi API + MCPEdge
Reliability16%2770Veryfi API + MCP +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5150Unstructured API + MCP +1
Agent ergonomics13%5875Veryfi API + MCP +17
Security & auth14%4744Unstructured API + MCP +3
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8068Unstructured API + MCP +12
Transparency & trust7%5859Veryfi API + MCP +1
Negative events≤15-60
TotalE 44.9/100C 60.6/100

Facts side by side

FactUnstructured API + MCPVeryfi API + MCP
KindHTTP APIHTTP API
VendorUnstructuredVeryfi
Hosted endpointhttps://transform.unstructured.io/api/v2https://api.veryfi.com/api/v8/partner
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0MIT (MCP server and SDKs)
Tools exposednone1
Read-only variant documentednono
llms.txtyesyes
MCP registryio.unstructured/transformnot listed
Last release2026-10-292026-09-15
Terms last updated2026-07-09couldn't be read
Privacy policy last updated2026-07-082026-07-10
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone31 stars, 5.7k npm/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Veryfi API + MCP higher.

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

Unstructured API + MCP

Apache-2.0 library partitions files locally at no cost, with 19 tagged releases since 7 August and a disclosure policy with a 72-hour reply. Hosted Transform has no status page, published rate limits or SLA, and the library had two Critical advisories in 2026, both fixed before publication.

Veryfi API + MCP

Typed fields and line items for receipts, invoices, cheques, bank statements and tax forms at $0.08 to $0.25 a document, with 100 free a month. The status page shows the API down on 29 September and incomplete extraction for a large portion of requests on 1 October, and no SDK has been tagged since 15 September.

Before you call either

Unstructured API + MCP

  1. For local ingestion, pip install "unstructured[all-docs]" at 0.24.1 or later and call partition(); no key needed, and set DO_NOT_TRACK=1 to stop telemetry
  2. Transform returns 202 with a Location header for long parses; poll it, then pass the parse id as parse_id to Extract
  3. Uploaded files expire after 24 hours; keep the original and re-upload on a 404
  4. Treat 409 parse_expired and 410 result_expired as a signal to rerun the parse, not to retry
  5. Library URL fetches refuse private and loopback addresses from 0.24.0; leave UNSTRUCTURED_ALLOW_PRIVATE_URL unset when partitioning untrusted URLs

Veryfi API + MCP

  1. Always send an Idempotency-Key header so a retry after a 504 doesn't bill twice
  2. Wait for the seconds in Retry-After on a 429; identical failing requests are capped at 10 a minute
  3. Set the CLIENT-ID header on every call
  4. Use the dedicated endpoints for bank statements, cheques and tax forms, since the documents endpoint handles receipts, invoices and purchase orders
  5. Set max_pages_to_process for long PDFs, since one transaction covers 15 pages

Questions

Which is better for AI agents, Unstructured API + MCP or Veryfi API + MCP?

Veryfi API + MCP scores 60.6 (C) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 3 of 7 scored categories. Unstructured API + MCP leads on maintenance & community.

Do Unstructured API + MCP and Veryfi API + MCP need an API key?

Unstructured API + MCP takes an API key or an OAuth sign-in. Veryfi API + MCP needs an API key.

Can an agent call Unstructured API + MCP and Veryfi API + MCP without installing anything?

Yes. Unstructured API + MCP has a hosted endpoint at https://transform.unstructured.io/api/v2 and Veryfi API + MCP at https://api.veryfi.com/api/v8/partner.

Are Unstructured API + MCP and Veryfi API + MCP open source?

Unstructured API + MCP is open source (Apache-2.0). No open-source release is listed for Veryfi API + MCP.

Other comparisons with Unstructured API + MCP or Veryfi API + MCP

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.