Nanonets API + MCP vs Unstructured API + MCP

Nanonets API + MCP

Extraction API returns Markdown, CSV or JSON, with named fields or a JSON schema. No public changelog and no dated release in the last 90 days.

Unstructured API + MCP

Apache-2.0 library partitions 45+ file types locally at no cost, tagged 11 times since 3 July. No status page, no published rate limits and no SLA.

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. Pass a JSON schema in json_options when downstream code needs fixed field names
3. Use the async extract endpoints for long documents and poll /api/v1/extract/results/{record_id}
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

Unstructured API + MCP

1. For local ingestion, pip install "unstructured[all-docs]" 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. Check for an existing job ID before resubmitting, since there's no idempotency key