Mindee API vs OpenDocRouter

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.

OpenDocRouter

One endpoint reaches 11 parsing models, each with a dated recipe version, a published token price and a ParseBench score, and failed pages aren't charged. The service launched on 7 October 2026, so it has no status page, incident history, SLA or changelog yet, and no key scopes were found in the reviewed documentation.

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

OpenDocRouter

1. Call GET /v1/models first, which needs no key, and choose a model by avg_charge_per_page_usd and its ParseBench scores. Send its id as model
2. Send cache: true on any request you might repeat. Without it the markdown exists only in the POST response and a resend is charged as a new request
3. Raise the SDK timeout above its 60-second default for sync parses. Pages can run for 270 seconds and the SDKs retry a timed-out request twice
4. Check every page's status before using its markdown. A 200 can be partial, and failed pages can be resent alone with pages
5. Treat 402 as final until credit is added. The hold is the model's maximum charge per page times the page count, and GET /v1/credits shows available_usd