Head to head · Document parsing · October 2026 research run

Extend API + MCP vs Unstructured API + MCP

Extend API + MCP scores 67.4 (B) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 5 of 7 scored categories. Unstructured API + MCP leads on payments & pricing. Both do document parsing.

Best document parsing, OCR and extraction APIs for AI agents · All 217 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 27
  • Schema & documentation, 87 against 51
  • Agent ergonomics, 68 against 58
  • Transparency & trust, 70 against 58

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 2.5 out of 5
  • No incidents deducted, where Unstructured API + MCP loses 6 points for them

Watch for

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

Unstructured API + MCP E

Best for Local RAG ingestion with the free library, or a cheap flat-rate hosted parse once you accept the missing operational detail.

Ahead on

  • Payments & pricing, 60 against 45

Also in its favour

  • Free to start without a card
  • Open source

Watch for

No status page, no published rate limits and no SLA

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.

Reliability Extend API + MCP +50

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.

Unstructured API + MCP 27

Readings on the docs and pricing pages are per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). No status page found, status.unstructured.io didn't resolve (0). No incident history to read (5). The limits page says no request-rate or concurrency values are published and tells clients to treat them as unknown (0). The recovery guide maps rate_limited to 429, says to back off and wait for Retry-After when it's sent, and says to check existing job IDs before resubmitting, safe-retry guidance with no idempotency key (12 of 15). No SLA found (0). Transform wasn't labelled beta in the pages read (10). 0+5+0+12+0+10 = 27.

Schema & documentation Extend API + MCP +36

Extend API + MCP 87

OpenAPI 3.1.0 at docs.extend.ai/openapi/api-reference.json, 76 paths and 117 operations on 2 November (25). llms.txt with a Markdown twin of every page (10). The MCP page now lists all 86 tools by group with a one-line purpose each; the tool definitions themselves still need an OAuth session. The API guides say what each processor is for and when to use the async endpoints (12 of 20). Typed request bodies in the spec, depth not re-checked (11 of 15). Error format with code, message, retryable, requestId and docUrl, seven general codes and domain codes on other pages (14 of 15). Dated API versions in the x-extend-api-version header, six of them back to 2024-02-01, plus a changelog of 42 entries with dated pages (15).

Unstructured API + MCP 51

All readings per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). No downloadable OpenAPI spec found; the per-endpoint API reference pages aren't a machine-readable contract (0). llms.txt, Markdown pages and an agent guide (10). Guides for parse, extract, chaining and jobs. MCP tool descriptions not read (12 of 20). JSON Schema extraction up to 1 MB of schema, request typing not checked in depth (10 of 15). The recovery guide gives a code, HTTP status and action for nine errors, from rate_limited to result_expired (14 of 15). Versioned /api/v2 path, no Transform changelog (5 of 15). 0+10+12+10+14+5 = 51.

Payments & pricing Unstructured API + MCP +15

Extend API + MCP 45

No x402, MPP or L402 (0). Credit prices and credits per page are published without a login, $0.01 a credit on pay as you go (20). Pay as you go starts with 10,000 free credits, and neither the pricing page nor the credits page says whether a card is needed (10 of 20, our call until that's confirmed). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Unstructured API + MCP 60

Pricing per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). No x402, MPP or L402 (0). $0.015 a page after the free pages, on the public pricing page (20). 10,000 free pages with no card (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust Extend API + MCP +12

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.

Unstructured API + MCP 58

The partitioning library is Apache-2.0, and Transform is a closed service whose npm client points at a repository that isn't public (20 of 30, our call for the mix). Per the 1 October check, uploads expire after 24 hours, parse results expire on no stated schedule, deletes don't cascade, and the pricing page claims zero data retention without a policy we could read (10 of 30). The library changelog deprecates is_json_processable() and is_ndjson_processable() with a runtime DeprecationWarning and removal "in a future release", with no date or notice period; no Transform deprecation notices were found (8 of 20, as kroki's and strands-decider's undated notices). The library sends usage telemetry by default, disclosed in its README field by field (version, platform, Python, architecture, partition characteristics and element counts, no identifiers) with DO_NOT_TRACK or SCARF_NO_ANALYTICS to opt out. No subprocessor list or data locations found for Transform (8 of 20). 20+10+8+8 = 46.

Agent ergonomics Extend API + MCP +10

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).

Unstructured API + MCP 58

All readings per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). The MCP tool count isn't published. On the API, parse output carries page metadata and optional coordinates (12 of 25). jobsList, jobsGet, cancel and delete endpoints (12 of 20). Every error code has a recovery action (18 of 20). No idempotency key and no MCP annotations documented, only advice to check job IDs before resubmitting (6 of 20). Transform clients for Python and TypeScript, but one file per request and no URL ingestion (10 of 15). 12+12+18+6+10 = 58.

Score by category

CategoryWeightExtend API + MCPUnstructured API + MCPEdge
Reliability16%7727Extend API + MCP +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8751Extend API + MCP +36
Agent ergonomics13%6858Extend API + MCP +10
Security & auth14%4547Unstructured API + MCP +2
Payments & pricing10%4560Unstructured API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8280Extend API + MCP +2
Transparency & trust7%7058Extend API + MCP +12
Negative events≤150-6
TotalB 67.4/100E 44.9/100

Facts side by side

FactExtend API + MCPUnstructured API + MCP
KindHTTP APIHTTP API
VendorExtendUnstructured
Hosted endpointhttps://api.extend.aihttps://transform.unstructured.io/api/v2
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for document parsing$5 per 1,000 pagesnot published
x402nono
LicencenoneApache-2.0
Tools exposed86none
Read-only variant documentednono
llms.txtyesyes
MCP registryai.extend/extendio.unstructured/transform
Last release2026-10-222026-10-29
Terms last updated2026-09-142026-07-09
Privacy policy last updated2026-09-142026-07-08
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 textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity124k npm/wk, 59k PyPI/wknone
Agent reviews4/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Extend API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

Unstructured API + MCP

Apache-2.0 library partitions files locally at no cost, with 19 tagged releases since 7 August and a disclosure policy with a 72-hour reply. Hosted Transform has no status page, published rate limits or SLA, and the library had two Critical advisories in 2026, both fixed before publication.

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

Unstructured API + MCP

  1. For local ingestion, pip install "unstructured[all-docs]" at 0.24.1 or later and call partition(); no key needed, and set DO_NOT_TRACK=1 to stop telemetry
  2. Transform returns 202 with a Location header for long parses; poll it, then pass the parse id as parse_id to Extract
  3. Uploaded files expire after 24 hours; keep the original and re-upload on a 404
  4. Treat 409 parse_expired and 410 result_expired as a signal to rerun the parse, not to retry
  5. Library URL fetches refuse private and loopback addresses from 0.24.0; leave UNSTRUCTURED_ALLOW_PRIVATE_URL unset when partitioning untrusted URLs

Questions

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

Extend API + MCP scores 67.4 (B) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 5 of 7 scored categories. Unstructured API + MCP leads on payments & pricing.

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

Both take an API key or an OAuth sign-in.

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

Yes. Extend API + MCP has a hosted endpoint at https://api.extend.ai and Unstructured API + MCP at https://transform.unstructured.io/api/v2.

Are Extend API + MCP and Unstructured API + MCP open source?

No open-source release is listed for Extend API + MCP. Unstructured API + MCP is open source (Apache-2.0).

Other comparisons with Extend API + MCP or Unstructured API + MCP

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.