Reducto API + MCP vs Unstructured API + MCP

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.

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.

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

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