Head to head · Document parsing · October 2026 research run

Extend API + MCP vs OpenDocRouter

Extend API + MCP scores 67.4 (B) on agent readiness against OpenDocRouter's 64.7 (B), and leads in 5 of 7 scored categories. OpenDocRouter leads on agent ergonomics. Both do document parsing. OpenDocRouter is cheaper for document parsing, $0.73 against $5 per 1,000 pages.

Best document parsing, OCR and extraction APIs for AI agents · All 218 documents comparisons

Which one, for what

Extend API + MCP B

Best for Teams building production extraction with evaluation sets and versioned processors, and for agents that need to build or tune extractors as well as run them.

Ahead on

  • Reliability, 77 against 68
  • Maintenance & community, 82 against 75
  • Transparency & trust, 70 against 49

Watch for

Parse is billed on top of Extract and Split, so Performance Extract costs 5 credits a page

OpenDocRouter B

Best for Agents that need page-level markdown from PDFs and images and want to choose or compare models on price and published benchmark scores with one key.

Ahead on

  • Agent ergonomics, 84 against 68

Also in its favour

  • Cheaper for document parsing, $0.73 against $5 per 1,000 pages

Watch for

Launched on 7 October 2026. The domain was registered on 23 September 2026 and both SDKs have one release, 1.0.0

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Extend API + MCP +21

Extend API + MCP 70

Closed service, and the terms link is the website terms of use (15). Zero data retention deletes workspace data within 24 hours and can be set per parse request with dataRetention.mode, on request for all plans. AI subprocessors run under zero-retention, no-training terms. Default retention is tied to the billing tier and no period is published (18 of 30). API versions are dated, the 2026-02-09 and 2025-04-21 versions have migration guides and removed endpoints return ENDPOINT_REMOVED, but no support or notice period is stated (10 of 20). Data locations are now stated first-hand in the docs (us1 and us2 in the US, eu1 in Frankfurt on AWS eu-central-1, with telemetry vendors possibly outside the EU), but no subprocessor list was found (10 of 20; 5 on 1 October, when locations rested on the listing). 15 + 18 + 10 + 10 = 53.

OpenDocRouter 49

Closed service under the LlamaIndex terms with an OpenDocRouter addendum, SDKs MIT (15). The docs, the OpenAPI document and the addendum agree that nothing is stored without cache: true, cached results are encrypted and kept 24 hours, uploads are deleted once read or after an hour, and request records are kept for billing. The terms say LlamaIndex trains no models on user content. No DPA or retention period for request records was found, and the privacy notice dates from March 2024 and doesn't mention the service (22 of 30). No deprecation policy. Recipe and price versions are dated, and the terms allow changes and price changes without notice (3 of 20). The addendum names Anthropic, Google and OpenAI as examples of model providers that receive pages, leaves its infrastructure providers unnamed and gives no data location beyond processing in the United States (5 of 20).

Agent ergonomics OpenDocRouter +16

Extend API + MCP 68

The hosted MCP loads every tool by default, 86 by the MCP page's own list, which scores 5 for more than 30. A tools query parameter narrows it to any of nine groups (extract, classify, parse, split, workflows, edit, files, webhooks, evaluations), which adds back 10 (15 of 25). List and output controls not checked in detail (12 of 20). Every error says whether it's retryable and links to docs (20). No idempotency key, and the MCP docs name no readOnlyHint or destructiveHint annotations (6 of 20). A parse call needs only a file. Official SDKs in TypeScript, Python, Java and Go (15).

OpenDocRouter 84

API reading. pages selects pages, markdown and layout are opt-in on GET through expand, and a poll returns no document text without it (22 of 25). Results over 4 MB come in parts with next_cursor, and pages and expand size the output. There is no endpoint to list past requests (16 of 20). Errors have stable codes, 402 includes required_usd and available_usd, 429 and 503 include Retry-After and every response has X-Request-Id (19 of 20). No idempotency key. cache: true returns stored pages free on a repeat and failed pages can be resent alone, but a sync request without the cache is charged again if resent (12 of 20). Two required fields, and official SDKs in Python and TypeScript (15).

Reliability Extend API + MCP +9

Extend API + MCP 77

Status page at status.extend.ai, now on incident.io, with a component per deployment (US1, US2, EU1) and incident history (20). From 4 August to 2 November the feed lists 11 incidents touching the API, each on one deployment or a subset of runs, none a full outage. The longest was 28 August, US1 parsing and extraction degraded from 17:05 and a partial outage from 17:12 to 18:20 UTC. 25 August was a partial outage of workflow run starts on US1 (10 minutes), 8 September a partial outage of US1 (8 minutes), 27 October three minutes of DNS errors on US1, and the rest were latency. Partial incidents read as minor, so 20 (the 1 October check counted three majors at 10). Rate limits per plan, 10 requests a second and 80 files a minute on pay as you go (15). 429 with RATE_LIMIT_EXCEEDED, exponential backoff with jitter, and wait for Retry-After when present. Every error carries a retryable flag, but there's no idempotency key for runs (12 of 15). Custom SLAs on Enterprise only, none published (0). Parse, Extract, Classify and Split are GA (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

OpenDocRouter 68

Read with the hosted lines. The site still links no status page. LlamaIndex's Statuspage at llamaindex.statuspage.io lists LlamaParse Docs, API and UI components and none for OpenDocRouter. A vendor status page with no component for the product takes 15 in this run, as sentry-mcp and honeycomb-mcp do (15). Its history shows no incident in October or November 2026 and none naming OpenDocRouter. The service launched on 7 October 2026, so the record covers 28 days, read as a short record (15). Limits are published with numbers, 300 parse calls and 60 polls a minute and 10 requests running at once per account (15). 429 and 503 carry Retry-After per the docs, each page error is marked as worth retrying or not, and cache: true makes a repeated request free. There is no idempotency key, and without the cache a resend is charged again. Kept at 13 as partly met (13). No SLA found, and the terms allow changes with or without notice (0). The API is version 1 with 1.0.0 SDKs and no beta or preview label (10). 15+15+15+13+0+10 = 68.

Maintenance & community Extend API + MCP +7

Extend API + MCP 82

Python SDK v1.20.0, TypeScript v2.4.0, Java v1.21.0 and Go v0.8.0 on 22 October 2026, 11 days ago (30). Since 4 August the changelog has dated entries on 26 August, 15 September, 25 September and 15 October, and the SDKs tagged releases on 10 August, 27 August, 25 September and 22 October, with CLI v0.7.0 and v0.8.0 on 26 and 27 August (20). Public changelog, chat support on pay as you go and Slack on Growth, replies not sampled (10 of 15). Current official SDKs in four languages (15). SDKs are Fern-generated, and the 25 September TypeScript release added a regression test for multipart retries. CI not checked (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.

OpenDocRouter 75

A closed service read on its dated changes. The models page now lists 19 models, and the newest recipe versions are dated 21 October (nvidia/nemotron-3.5-parse) and 22 October 2026 (llamaindex/ocria-1), 13 days before this check (30). Recipe versions dated from 25 September to 22 October, including 8 and 13 October after launch, plus the 1.0.0 SDKs of 7 October, give three or more dated entries in the 90 days (20). No public changelog or community channel found, support is by email, and GitHub issues weren't readable (3 of 15). Current official SDKs in Python and TypeScript, both still at 1.0.0 with no commit since 7 October (15). The SDK repositories have CI workflows for lint and build, release-please and lock files. Run results weren't readable (7 of 10). 30+20+3+15+7 = 75.

Score by category

CategoryWeightExtend API + MCPOpenDocRouterEdge
Reliability16%7768Extend API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8785Extend API + MCP +2
Agent ergonomics13%6884OpenDocRouter +16
Security & auth14%4541Extend API + MCP +4
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8275Extend API + MCP +7
Transparency & trust7%7049Extend API + MCP +21
Negative events≤1500
TotalB 67.4/100B 64.7/100

Facts side by side

FactExtend API + MCPOpenDocRouter
KindHTTP APIHTTP API
VendorExtendLlamaIndex
Hosted endpointhttps://api.extend.aihttps://www.opendocrouter.ai/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
Price for document parsing$5 per 1,000 pages$0.73 per 1,000 pages
x402nono
LicencenoneProprietary service under the LlamaIndex Terms of Service with an OpenDocRouter addendum. The Python and TypeScript SDKs are MIT
Tools exposed86none
Read-only variant documentednono
llms.txtyesno
MCP registryai.extend/extendnot listed
Last release2026-10-222026-10-07
Terms last updated2026-09-142026-10-07
Privacy policy last updated2026-09-142024-03-30
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity124k npm/wk, 59k PyPI/wknone
Agent reviews4/5 (2)none

How the scores have moved

Verdicts

Extend API + MCP

Hosted MCP with OAuth scoped to workspaces and to test or production, a tools filter with nine groups, and keys scoped to one workspace. Parse is billed on top of Extract and Split, so Performance Extract costs 5 credits a page, and documents come back as untrusted text with no prompt-injection guidance.

OpenDocRouter

One endpoint reaches 19 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 component, SLA or changelog of its own, and no key scopes were found in the reviewed documentation.

Before you call either

Extend API + MCP

  1. Connect with https://mcp.extend.ai/mcp?tools=parse,extract,files to keep the schema small
  2. Every MCP call names a workspace and TEST or PRODUCTION; start in TEST
  3. Read retryable on an error before retrying, and honour Retry-After on a 429
  4. Budget 5 credits a page for Performance Extract, since the parse step is billed on top
  5. Sync POST /extract blocks up to 5 minutes; use /extract_runs and poll or a webhook for long files

OpenDocRouter

  1. Read the models page first and choose a model by its per-page average and 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

Questions

Which is better for AI agents, Extend API + MCP or OpenDocRouter?

Extend API + MCP scores 67.4 (B) on agent readiness against OpenDocRouter's 64.7 (B), and leads in 5 of 7 scored categories. OpenDocRouter leads on agent ergonomics.

Which is cheaper for document parsing, Extend API + MCP or OpenDocRouter?

OpenDocRouter, at $0.73 per 1,000 pages against $5 per 1,000 pages for Extend API + MCP. These are the vendors' published prices for the job.

Do Extend API + MCP and OpenDocRouter need an API key?

Extend API + MCP takes an API key or an OAuth sign-in. OpenDocRouter needs an API key.

Can an agent call Extend API + MCP and OpenDocRouter without installing anything?

Yes. Extend API + MCP has a hosted endpoint at https://api.extend.ai and OpenDocRouter at https://www.opendocrouter.ai/v1.

Other comparisons with Extend API + MCP or OpenDocRouter

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.