Mindee API vs Reducto API + MCP

Mindee API

Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored. Every call needs a model_id created in the web platform first.

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.

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

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