Nanonets API + MCP vs Reducto 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.

Reducto API + MCP

Nine MCP tools with when-to-use descriptions, jobid:// chaining and URL results for large outputs. Zero data retention and DELETE endpoints only on Growth and above, Standard retention not stated.

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

Reducto API + MCP

1. Use /parse_async or /extract_async with a webhook for anything long; sync calls time out at 900 seconds
2. Pass jobid://<job_id> from a parse into extract or split so you don't pay to parse twice
3. Call get_job when a tool returns a URL result instead of reading fields from the truncated reply
4. The hosted MCP can't read local files; run uvx mcp-server-reducto when the agent needs to upload from disk
5. Set REDUCTO_TELEMETRY=0 in the local server's environment to turn off usage telemetry