Nanonets API + MCP vs OpenDocRouter

Nanonets API + MCP

Extraction API returns Markdown, CSV or JSON, with named fields or a JSON schema. No public changelog and no dated release in the last 90 days.

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.

Nanonets API + MCP

1. Use the extraction API at extraction-api.nanonets.com, not app.nanonets.com, unless you already have a trained model
2. Pass a JSON schema in json_options when downstream code needs fixed field names
3. Use the async extract endpoints for long documents and poll /api/v1/extract/results/{record_id}
4. On a 429, wait 30 seconds and double the delay each retry
5. Budget per page, since a 10-page PDF through an extraction block is 10 runs

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