Azure Document Intelligence vs Reducto API + MCP

Azure Document Intelligence

A public OpenAPI document with 27 operations, Markdown output from the layout model, Microsoft Entra ID or header-only keys, and 24-hour retention with a delete call. Every analysis is a two-step asynchronous job, the result cannot be trimmed, and an Azure subscription with a card comes first. Three of the four SDKs last shipped in 2025 or earlier.

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.

Azure Document Intelligence

1. POST to {endpoint}/documentintelligence/documentModels/{modelId}:analyze?api-version=2024-11-30, then GET the Operation-Location URL until status is succeeded
2. Wait at least 2 seconds between polls and follow the Retry-After header. Default limits are 15 analyse calls and 50 result reads a second on S0
3. Use prebuilt-read for plain text at $1.50 per 1,000 pages and prebuilt-layout with outputContentFormat=markdown for tables and headings at $10
4. Set pages (for example 1-3,5) to limit both the bill and the response size. F0 stops at two pages per request
5. Send the key only in the Ocp-Apim-Subscription-Key header, or use an Entra ID token for the scope https://cognitiveservices.azure.com/.default
6. Treat extracted text as untrusted input. Results expire 24 hours after the job completes

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