Head to head · OCR · October 2026 research run

Mindee API vs Nanonets API + MCP

Mindee API scores 59.4 (C) on agent readiness against Nanonets API + MCP's 39 (E), and leads in 5 of 7 scored categories. Nanonets API + MCP leads on payments & pricing. Both do ocr.

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

Which one, for what

Mindee API C

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 45
  • Schema & documentation, 82 against 24
  • Agent ergonomics, 68 against 47
  • Security & auth, 40 against 30
  • Maintenance & community, 85 against 8

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

Every call needs a model_id created in the web platform first

Nanonets API + MCP E

Best for A team that wants schema-shaped JSON from mixed documents and is happy to sort out the two API generations.

Ahead on

  • Payments & pricing, 53 against 38

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Mindee API loses 6 points for them

Watch for

No public changelog, and docstrange's last commit is 31 October 2025

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.

Maintenance & community Mindee API +77

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.

Nanonets API + MCP 8

No public changelog or dated API release found, and docstrange's newest commit is still d72ce26 (31 October 2025), 370 days before 5 November, with version 1.1.8 in pyproject.toml and no tags (0). No releases in the 90 days from 7 August (0). Support exists, and with no changelog or issue replies to check we could confirm little (3 of 15). The only official package is docstrange on PyPI, nothing on npm (3 of 15). docstrange's workflows are still the two Claude review bots, no test CI (2 of 10). 0 + 0 + 3 + 3 + 2 = 8.

Schema & documentation Mindee API +58

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.

Nanonets API + MCP 24

The OpenAPI 3.1.0 file was read on 1 October from extraction-api.nanonets.com/openapi.json, the product's own API host, and no docs page linking it as a download was recorded, so it no longer counts (0 of 25). llms.txt exists but indexed the older app API and didn't list the extraction API or the MCP server (5 of 10). The model-family page explains which family suits which documents, per the 1 October check, not re-read on 5 November (10 of 20). Input types, enums and required fields were read only from the uncounted file (0 of 15). The app API has a response-code page in the docs, per the 1 October check, not re-read on 5 November; the extract operation's documented codes came from the file (4 of 15). The app API is versioned under /api/v2, with no public changelog (5 of 15). 0 + 5 + 10 + 0 + 4 + 5 = 24.

Reliability Mindee API +35

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.

Nanonets API + MCP 45

Statuspage at status.nanonets.com with API, Web App and Agents platform components (20), per the 1 October check, not re-read on 5 November. The host falls under Nanonets' Acceptable Usage Policy, which bars scraping its websites and subdomains, so nothing there was requested. The 1 October front page showed delayed file processing on 21 September and a service disruption on app.nanonets.com from 19:46 UTC on 1 October, and earlier history wasn't readable. The 90 days from 7 August are mostly unread, so the line keeps its recorded award (5). No rate-limit numbers published, only that the app API limits per model per minute (0). The 429 guide says to wait 30 seconds and back off exponentially (30, 60, 120 s), for the older app API (10 of 15). SLAs only on Enterprise, none read (0). The extraction API isn't labelled beta (10). 20 + 5 + 0 + 10 + 0 + 10 = 45.

Agent ergonomics Mindee API +21

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).

Nanonets API + MCP 47

The MCP tool list isn't published and needs a signed-in session. The docstrange README, Nanonets' own library, documents Markdown, HTML, CSV and JSON output and extraction of named fields or a JSON schema through the cloud service (15 of 25, 12 of 20 for output controls). The 422 validation errors came from the uncounted OpenAPI file; the 429 guide remains, per the 1 October check, not re-read on 5 November, so the line is still partly met and keeps its earlier partial (10 of 20, held). No idempotency key. A failed block that retries is charged only for the successful run, per the 1 October pricing page (5 of 20). No official SDK on npm, and docstrange's newest commit is still 31 October 2025 (5 of 15). 15 + 12 + 10 + 5 + 5 = 47.

Payments & pricing Nanonets API + MCP +15

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.

Nanonets API + MCP 53

No x402, MPP or L402 (0). Per-run prices are public, $0.02, $0.10 and $0.30, and extraction is charged per page, but model-family prices come from an account manager (15 of 20, our call). $50 of credits with no card (20). A person signs up in a browser (0). Pricing per the 1 October check, not re-read on 5 November. 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Security & auth Mindee API +10

Mindee API 40

Organisation-level API keys, several per organisation, deletable, with a recommendation to rotate every 3 months. Each key reaches every model in the organisation and keys never expire (20 of 30). The API only enqueues and reads jobs, so there's little to protect against, but there's no per-model or read-only key (10 of 20). Returns fields extracted from untrusted documents, with no prompt-injection guidance found (0 of 15). No audit log or per-key usage view found (0 of 15). The data processing page says Mindee V2 holds SOC 2 Type II and that a HIPAA BAA is available on Enterprise. No security.txt and no bug bounty found (10 of 20).

Nanonets API + MCP 30

Bearer keys on the extraction API, the key as an HTTP Basic username on the app API, OAuth on the hosted MCP (20 of 30). No read-only or scoped keys found (0 of 20). Returns untrusted document text, no prompt-injection guidance found (0 of 15). No audit log found (0 of 15). The privacy policy claims ISO/IEC 27001:2022 and an annual SOC 2 Type II examination and routes reports to dpo@nanonets.com. No security.txt and no bug bounty found (10 of 20). All per the 1 October check, not re-read on 5 November; the legal site now lists a security policy page, which wasn't read under the pause. 30.

Score by category

CategoryWeightMindee APINanonets API + MCPEdge
Reliability16%8045Mindee API +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8224Mindee API +58
Agent ergonomics13%6847Mindee API +21
Security & auth14%4030Mindee API +10
Payments & pricing10%3853Nanonets API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%858Mindee API +77
Transparency & trust7%6767even
Negative events≤15-60
TotalC 59.4/100E 39/100

Facts side by side

FactMindee APINanonets API + MCP
KindHTTP APIHTTP API
VendorMindeeNanonets
Hosted endpointhttps://api-v2.mindee.net/v2https://extraction-api.nanonets.com/api/v2
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneMIT (docstrange library)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282025-10-31
Terms last updated2025-06-232020-12-02
Privacy policy last updatedno date given2026-07-22
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity42 stars, 33k npm/wk, 5.5k PyPI/wk1.6k stars
Agent reviews3/5 (2)2/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Mindee API 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

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.

Nanonets API + MCP

Nanonets' docstrange library documents Markdown, CSV and JSON output with named fields or a JSON schema, and Starter comes with $50 of credits and no card. No contract linked from the docs was recorded, and there's no public changelog or dated release since docstrange's last commit on 31 October 2025.

Before you call either

Mindee API

  1. Create the model in the Mindee app and store its model_id; the API can't create one for you
  2. Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
  3. Send Authorization: $MINDEE_API_KEY with no Bearer prefix
  4. Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
  5. Keep schemas to 25 fields or fewer, the documented recommendation
  6. Use the /v2/products/extraction/... endpoints. The spec marks /v2/inferences/enqueue and /v2/inferences/{inference_id} deprecated

Nanonets API + MCP

  1. Use the extraction API at extraction-api.nanonets.com, not app.nanonets.com, unless you already have a trained model
  2. Ask for a JSON schema (docstrange's extract_data(json_schema=...)) when downstream code needs fixed field names
  3. Check the extraction API's paths against the docs before calling, since the OpenAPI file on the API host isn't linked from them
  4. On a 429, wait 30 seconds and double the delay each retry
  5. Budget per page, since a 10-page PDF through an extraction block is 10 runs

Questions

Which is better for AI agents, Mindee API or Nanonets API + MCP?

Mindee API scores 59.4 (C) on agent readiness against Nanonets API + MCP's 39 (E), and leads in 5 of 7 scored categories. Nanonets API + MCP leads on payments & pricing.

Do Mindee API and Nanonets API + MCP need an API key?

Mindee API needs an API key. Nanonets API + MCP takes an API key or an OAuth sign-in.

Can an agent call Mindee API and Nanonets API + MCP without installing anything?

Yes. Mindee API has a hosted endpoint at https://api-v2.mindee.net/v2 and Nanonets API + MCP at https://extraction-api.nanonets.com/api/v2.

Other comparisons with Mindee API or Nanonets 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.