Datalab vs Nanonets API + MCP

Datalab 79

Closed hosted service. Python SDK 0.9.1 on 6 November 2026 and a changelog entry on 4 November (30). Over twenty dated changelog entries since 8 August (20). Support by email, a Discord and public GitHub repositories for the open-source models; replies not sampled (12 of 15). An official Python SDK, current, no other languages (12 of 15). Package health not checked beyond release dates (5 of 10). 30+20+12+12+5 = 79.

Nanonets API + MCP 8

No public changelog or dated API release found, and docstrange's newest commit is 2025-10-31, 11 months ago (0). No releases in the last 90 days found (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 Claude review bots, no test CI (2 of 10).

Datalab 89

An OpenAPI 3.1 operation embedded in each reference page (spec version 0.0.1), no single downloadable file found (22 of 25). llms.txt with 159 pages and Markdown twins (10). Recipes say when to use each processor and mode (15 of 20). Typed request schemas with enums for output format and mode (12 of 15). An error table with type, HTTP code and whether to retry, plus SDK exception mapping (15). A written version policy and a dated changelog (15). 22+10+15+12+15+15 = 89.

Nanonets API + MCP 61

OpenAPI 3.1.0 at extraction-api.nanonets.com/openapi.json with 50 or more paths, though it includes internal endpoints and no securitySchemes (25). llms.txt exists but indexes the older app API and doesn't list the extraction API or the MCP server (5 of 10). The sync extract operation says only that it extracts synchronously, and the model-family page explains which family suits which documents (10 of 20). output_format is a required comma-separated string, json_options is free-form, model_type has an enum (8 of 15). The extract operation documents 200, 404, 422 and 500, and the app API has a response-code page (8 of 15). v1 and v2 paths, no public changelog (5 of 15).

Datalab 73

Output as Markdown, HTML, JSON or chunks, page_range to limit pages, and cost_breakdown on results (20 of 25). File listing and pipeline endpoints, little else to paginate (14 of 20). Typed errors with retry guidance an agent can follow (18 of 20). No idempotency key; the docs say to poll a known request ID instead of resubmitting, and webhooks may be retried (12 of 20). Official Python SDK and CLI, one language (9 of 15). 20+14+18+12+9 = 73.

Nanonets API + MCP 47

The MCP tool list isn't published and needs a signed-in session. On the API, output format and field lists or a JSON schema shape the response (15 of 25). Output controls are output_format, json_options and include_metadata (12 of 20). 422 validation errors and the 429 guide (10 of 20). No idempotency key. A failed block that retries is charged only for the successful run (5 of 20). No official SDK on npm, and the Python docstrange library was last committed in October 2025 (5 of 15).

Datalab 56

Several hashed API keys with per-key 30-day spend caps, revoke-and-replace rotation, no scopes (24 of 30). Spend caps limit damage; results and files can be deleted by the key holder, and there's no read-only key (10 of 20). Returns document text with no prompt-injection guidance (2 of 15). cost_breakdown per request and usage tracking in the dashboard (8 of 15). A Secureframe trust centre and a SOC 2 report on the Team plan, TOTP enforcement for teams; no disclosure policy or security.txt found (12 of 20). 24+10+2+8+12 = 56.

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

Datalab 58

Hosted lines. Status page at status.datalab.to (incident.io) with Website and Datalab API components; the history page is drawn by script, so components are confirmed and history isn't (15 of 20, 5 for history). Rate limits per plan with numbers, plus page and size limits (15). 429 is retryable with sample backoff, and 500 and 529 say to check a known request ID before resubmitting; webhooks deduplicate by request_id (13 of 15). Custom SLAs only for Enterprise (0). Generally available (10). 15+5+15+13+0+10 = 58.

Nanonets API + MCP 45

Statuspage at status.nanonets.com with API, Web App and Agents platform components (20). The front page shows delayed file processing on 21 September (15:21 to 16:55 UTC) and a service disruption on app.nanonets.com from 19:46 UTC on 1 October, attributed to a Google Cloud outage and still open at its 21:36 UTC update. Earlier history wasn't readable (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 published (0). The extraction API isn't labelled beta (10).

Datalab 40

No x402, MPP or L402 (0). Per-1,000-page rates for every processor and add-on on the public pricing page (20). A $10 to $20 monthly allowance with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40.

Nanonets API + MCP 35

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