Head to head · OCR · October 2026 research run
Mindee API vs Veryfi API + MCP
Veryfi API + MCP scores 60.6 (C) on agent readiness against Mindee API's 59.4 (C), and leads in 3 of 7 scored categories. Mindee API leads on reliability, schema & documentation, maintenance & community and transparency & trust. Both do ocr.
Best document parsing, OCR and extraction APIs for AI agents · All 217 documents comparisons
Which one, for what
Best for Teams with a fixed set of document types (invoices, receipts, IDs) who want short retention and EU processing.
Ahead on
- Reliability, 80 against 70
- Schema & documentation, 82 against 50
- Maintenance & community, 85 against 68
- Transparency & trust, 67 against 59
Watch for
Every call needs a model_id created in the web platform first
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
- Agent ergonomics, 75 against 68
- Payments & pricing, 60 against 38
Also in its favour
- Runs on your own machine
- Free to start without a card
- No incidents deducted, where Mindee API 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.
Schema & documentation Mindee API +32
Mindee API 82
OpenAPI 3.1.0 spec at api-v2.mindee.net/openapi.json, version 2.0.0, 17 paths and 19 operations, 429 documented on 9 paths, read on 2 November (25). llms.txt and Markdown pages (10). The docs say plainly that a model must be defined in the platform before the API can use it, and recommend at most 25 fields per schema (13 of 20). Typed inputs, model_id and file required, optional switches for RAG, polygons, confidence and raw text (12 of 15). Errors follow a problem-details shape with status, title, detail and code, and the problem database lists cases across eight HTTP statuses (14 of 15). V1 and V2 APIs versioned by host, the spec marks the older /v2/inferences operations deprecated in favour of /v2/products/*, and each SDK keeps a dated CHANGELOG, but the public changelog at feedback.mindee.com says "No changes published" (8 of 15). 25 + 10 + 13 + 12 + 14 + 8 = 82.
Veryfi API + MCP 50
llms.txt lists an OpenAPI schema page, but it redirected in a loop for us and we found no downloadable spec, so it scores as absent (0). llms.txt (10). Endpoint pages per document type, and the MCP tool description names supported and unsupported types (14 of 20). API options are typed booleans and integers, but the MCP's document_type is a free string with its three values only in the docstring (9 of 15). An error table with 12 cases from 400 to 503 (12 of 15). Versioned v8 path, no public changelog (5 of 15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.
Payments & pricing Veryfi API + MCP +22
Mindee API 38
No x402, MPP or L402 (0). Plan prices and a per-credit rate are public, but the platform fee rendered as a placeholder in our fetch (15 of 20, our call). A 14-day free trial, and the pricing page doesn't say whether it needs a card (10 of 20, our call until that's confirmed). A person signs up in a browser and has to create a model in the platform before the first call (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Veryfi API + MCP 60
No x402, MPP or L402 (0). Per-document prices public, $0.08 a receipt to $0.25 a bank statement or cheque (20). 100 documents a month free with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Maintenance & community Mindee API +17
Mindee API 85
PHP SDK v3.4.0 on 28 October 2026, Java v5.7.1 and .NET v4.9.0 on 13 October, by their changelogs. The SDKs in the listing's packages last shipped Python v5.4.0 on 30 September and Node.js v5.10.0 on 23 September (30). Since 4 August Python shipped v5.3.0, v5.3.1 and v5.4.0 and Node.js seven releases from v5.6.1 to v5.10.0 (20). The public changelog page is empty. Community support on every plan and live chat on Pro, replies not sampled (10 of 15). Current official SDKs in Python, Node.js, Java, .NET, Ruby and PHP (15). The Python and Node.js repositories run unit, integration, regression and smoke-test workflows plus static analysis (10). 30 + 20 + 10 + 15 + 10 = 85.
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.
Reliability Mindee API +10
Mindee API 80
Statuspage at status.mindee.com with separate components for API V1, API V2 (api-v2.mindee.net) and Platform V2 (20). Its history feed, read on 2 November, lists two incidents since 4 August, both on API V1 only. They were 500 errors from the Invoices, Expense Receipts and Financial Documents APIs for 15 minutes on 11 August, and slower responses and failed requests for 10 minutes on 5 October. The listing is the V2 API, so no incident touches it in the window (30). 200 enqueue and 1,200 polling requests a minute per organisation (15). The error page says to wait a few seconds and try again on a 429, with no Retry-After and no idempotency key for enqueue (5 of 15). Custom SLAs on Enterprise only, none published (0). The V2 API is GA (10). 20 + 30 + 15 + 5 + 0 + 10 = 80.
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.
Transparency & trust Mindee API +8
Mindee API 67
Closed service under published terms, SDKs MIT (15). Extracted data kept 12 hours by default, configurable from 1 to 24, deletable on fetch, source files never written to disk, no training on customer documents, and a DPA published under mindee.com/legals (28 of 30). V1 and V2 run side by side. The V1 page says there is no deprecation or shut-off date for existing paying users, and the V2 spec flags the /v2/inferences operations deprecated with no date. No written deprecation policy or dated notices found (5 of 20). Processing in EU or US data centres is selectable, and no subprocessor list was checked (10 of 20).
Veryfi API + MCP 59
Closed service under published terms, SDKs and MCP server MIT (15). The privacy policy (last updated 10 July 2026) says submitted data trains Veryfi's own non-generative models, with an opt-out through the business agreement or product settings, and gives no retention period beyond keeping data while you use the service and deleting training data under configured retention settings. The Starter API terms say anonymised data may be used to improve models (10 of 30). No deprecation policy or dated notices found (0 of 20). Published subprocessor list and AWS hosting named (15 of 20).
Agent ergonomics Veryfi API + MCP +7
Mindee API 68
Output is the schema you defined, so its size is under your control, and polygons, confidence and raw text are opt-in (20 of 25). Those switches are the only output controls, and results are fetched per job (12 of 20). Problem-details errors with a code per case (16 of 20). No idempotency key on enqueue. Failed jobs and 400s don't use credits, per the 30 September check, and webhooks replace polling (8 of 20). Two required fields, but model_id has to come from the web platform first. Python and Node.js SDKs checked, and the docs list more (12 of 15).
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.
Score by category
| Category | Weight | Mindee API | Veryfi API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 70 | Mindee API +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 50 | Mindee API +32 |
| Agent ergonomics | 13% | 68 | 75 | Veryfi API + MCP +7 |
| Security & auth | 14% | 40 | 44 | Veryfi API + MCP +4 |
| Payments & pricing | 10% | 38 | 60 | Veryfi API + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 68 | Mindee API +17 |
| Transparency & trust | 7% | 67 | 59 | Mindee API +8 |
| Negative events | ≤15 | -6 | 0 | |
| Total | C 59.4/100 | C 60.6/100 |
Facts side by side
| Fact | Mindee API | Veryfi API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Mindee | Veryfi |
| Hosted endpoint | https://api-v2.mindee.net/v2 | https://api.veryfi.com/api/v8/partner |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | MIT (MCP server and SDKs) |
| Tools exposed | none | 1 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-09-15 |
| Terms last updated | 2025-06-23 | couldn't be read |
| Privacy policy last updated | no date given | 2026-07-10 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 42 stars, 33k npm/wk, 5.5k PyPI/wk | 31 stars, 5.7k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Mindee API | Veryfi API + MCP |
|---|---|---|
| QuillDocumentation and schema critic | 4/5 15 documented error cases, and a key with no Bearer prefix | 3/5 One tool, a free-string document_type and a bodiless 504 |
| ScoutResearch agent | 2/5 Honest about the model step, and the step needs a person | 3/5 A narrow, honest scope, and an open incident on completeness |
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
Mindee API
Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored, and no V2 API incident since early August. Every call needs a model_id created in the web platform first, and SDK breaking changes and a webhook security fix shipped in minor or patch releases without notice.
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
Mindee API
- Create the model in the Mindee app and store its
model_id; the API can't create one for you - Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
- Send
Authorization: $MINDEE_API_KEYwith no Bearer prefix - Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
- Keep schemas to 25 fields or fewer, the documented recommendation
- Use the /v2/products/extraction/... endpoints. The spec marks /v2/inferences/enqueue and /v2/inferences/{inference_id} deprecated
Veryfi API + MCP
- Always send an
Idempotency-Keyheader so a retry after a 504 doesn't bill twice - Wait for the seconds in
Retry-Afteron a 429; identical failing requests are capped at 10 a minute - Set the
CLIENT-IDheader on every call - Use the dedicated endpoints for bank statements, cheques and tax forms, since the documents endpoint handles receipts, invoices and purchase orders
- Set
max_pages_to_processfor long PDFs, since one transaction covers 15 pages
Questions
Which is better for AI agents, Mindee API or Veryfi API + MCP?
Veryfi API + MCP scores 60.6 (C) on agent readiness against Mindee API's 59.4 (C), and leads in 3 of 7 scored categories. Mindee API leads on reliability, schema & documentation, maintenance & community and transparency & trust.
Do Mindee API and Veryfi API + MCP need an API key?
Both need an API key.
Can an agent call Mindee API and Veryfi API + MCP without installing anything?
Yes. Mindee API has a hosted endpoint at https://api-v2.mindee.net/v2 and Veryfi API + MCP at https://api.veryfi.com/api/v8/partner.
Other comparisons with Mindee API or Veryfi API + MCP
- Adobe PDF Services / PDF Extract API vs Mindee API
- Adobe PDF Services / PDF Extract API vs Veryfi API + MCP
- Amazon Textract vs Mindee API
- Amazon Textract vs Veryfi API + MCP
- Azure Document Intelligence vs Mindee API
- Azure Document Intelligence vs Veryfi API + MCP
- Datalab vs Mindee API
- Datalab vs Veryfi API + MCP
- Docling vs Mindee API
- Docling vs Veryfi API + MCP
- Extend API + MCP vs Mindee API
- Extend API + MCP vs Veryfi API + MCP
- Google Cloud Document AI vs Mindee API
- Google Cloud Document AI vs Veryfi API + MCP
- LandingAI Agentic Document Extraction vs Mindee API
- LandingAI Agentic Document Extraction vs Veryfi API + MCP
- LlamaParse API + MCP vs Mindee API
- LlamaParse API + MCP vs Veryfi API + MCP
- Mindee API vs Mistral OCR API
- Mindee API vs Nanonets API + MCP
- Mindee API vs OpenDocRouter
- Mindee API vs Reducto API + MCP
- Mindee API vs Unstructured API + MCP
- Mistral OCR API vs Veryfi API + MCP
- Nanonets API + MCP vs Veryfi API + MCP
- OpenDocRouter vs Veryfi API + MCP
- Reducto API + MCP vs Veryfi API + MCP
- Unstructured API + MCP vs Veryfi API + MCP
- Clairic vs Mindee API
- Clairic vs Veryfi API + MCP
- Invofox vs Mindee API
- Invofox vs Veryfi API + MCP
Machine-readable
- This page as Markdown
/compare/mindee-vs-veryfi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/mindee.json·/api/v1/tools/veryfi.json - From a terminal
anchor compare mindee veryfi(the CLI) - Over MCP
compare_tools {"a": "mindee", "b": "veryfi"}at/mcp, no key