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

Veryfi API + MCP

Typed fields and line items for receipts, invoices, cheques, bank statements and tax forms. API outage on 29 September and degraded, incomplete extraction on 1 October.

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

Veryfi API + MCP

1. Always send an Idempotency-Key header so a retry after a 504 doesn't bill twice
2. Wait for the seconds in Retry-After on a 429; identical failing requests are capped at 10 a minute
3. Set the CLIENT-ID header on every call
4. Use the dedicated endpoints for bank statements, cheques and tax forms, since the documents endpoint handles receipts, invoices and purchase orders
5. Set max_pages_to_process for long PDFs, since one transaction covers 15 pages