Head to head · Document parsing · October 2026 research run

Adobe PDF Services / PDF Extract API vs Unstructured API + MCP

Adobe PDF Services / PDF Extract API scores 56.2 (C) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 4 of 7 scored categories. Unstructured API + MCP leads on payments & pricing and maintenance & community. Both do document parsing.

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

Best PDF manipulation and conversion APIs for AI agents · All 58 pdf comparisons

Which one, for what

Adobe PDF Services / PDF Extract API C

Best for Teams already on Adobe that want PDF extraction and PDF manipulation on one credential, with EU processing.

Ahead on

  • Reliability, 50 against 27
  • Schema & documentation, 80 against 51
  • Security & auth, 55 against 47
  • Transparency & trust, 78 against 58

Also in its favour

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

Watch for

No published paid price, paid use goes through sales

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 30
  • Maintenance & community, 80 against 43

Also in its favour

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

Maintenance & community Unstructured API + MCP +37

Adobe PDF Services / PDF Extract API 43

Python SDK 4.3.0 and .NET SDK 4.4.0 shipped on 10 August 2026, 86 days before 4 November, the newest entries in the release notes and the newest tag in the Python SDK repository (20). Those two, on the same day, are the only release-note entries in the 90 days from 6 August, and the one before them was .NET SDK 4.3.1 on 29 September 2025. Fewer than three, so the line gives 0 (was 10, a value the line doesn't have). Public release notes and Adobe's developer forums, replies not sampled (10 of 15). Python and .NET SDKs are current, the Java samples still pin 4.3.0 from April 2025 and the Node.js samples 4.1.0 from November 2024 (10 of 15). The Python SDK repository has a publish workflow and no test workflow (3 of 10). 20+0+10+10+3 = 43.

Unstructured API + MCP 80

The open-source library, a listed package, was tagged 0.27.36 on 29 October 2026, 7 days before this check (30). It has 19 tags in the 90 days from 7 August, from 0.27.0 (21 August) to 0.27.36 (20). The library repository is public and active; per the 1 October check the Transform repository its npm client points to isn't public, and there's no Transform changelog (8 of 15). Transform clients for Python and TypeScript, per the 1 October check (15). The library runs CI, CodeQL and benchmark workflows; the Transform code can't be inspected (7 of 10). 30+20+8+15+7 = 80.

Payments & pricing Unstructured API + MCP +30

Adobe PDF Services / PDF Extract API 30

No x402, MPP or L402 (0). The pricing page publishes the free tier and the transaction rules (1 transaction per 5 pages for Extract) but no paid price, which goes through sales (0). 500 Document Transactions a month free with no card (20). A person signs up for an Adobe account in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

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.

Schema & documentation Adobe PDF Services / PDF Extract API +29

Adobe PDF Services / PDF Extract API 80

OpenAPI 3.0.1 spec with 48 paths, including /operation/extractpdf and /operation/pdftomarkdown, published in the AdobeDocs/pdfservices-api-documentation repository and rendered as the API reference (25). No llms.txt, developer.adobe.com/document-services/llms.txt returns 404 (0). The Extract description lists what each option returns, and an API limitations section says when not to use it (XFA forms, CAD drawings, non-English text, scans under 200 DPI) (16 of 20). Typed request bodies with enums for elementsToExtract and renditionsToExtract and stated defaults, though tableOutputFormat is a free string (12 of 15). An error-code table for Extract (at least 16 named codes, such as DISQUALIFIED_PAGE_LIMIT and BAD_PDF_COMPLEX_TABLE) and request examples in the spec (12 of 15). Dated release notes and a written semver policy for the SDKs (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.

Reliability Adobe PDF Services / PDF Extract API +23

Adobe PDF Services / PDF Extract API 50

The docs point to a PDF Services product page at status.adobe.com/products/512699, which renders only with JavaScript, so its component history couldn't be confirmed (15 of 20, per the 1 October check, not re-read on 4 November, since Adobe's hosts are paused for this run) and no incident could be read (5). Rate limits are published in the docs repository, 25 requests a minute on the free tier and 100 on enterprise, unchanged on 4 November (15). The OpenAPI spec documents a 429 on every operation, described as insufficient quota, with no Retry-After header and no backoff guidance in the docs, re-read from the AdobeDocs repository on 4 November (5 of 15, partly met, kept). No SLA found (0). Extract and PDF to Markdown aren't labelled beta (10). 15+5+15+5+0+10 = 50.

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.

Transparency & trust Adobe PDF Services / PDF Extract API +20

Adobe PDF Services / PDF Extract API 78

Closed service under Adobe's terms, and the SDKs ship under Adobe's own licence agreement rather than an OSI licence (15). The PDF Services security page says uploads and outputs stay in Document Cloud for 24 hours by default, can be deleted at once with DELETE /assets, and can bypass Adobe storage through signed URLs. We didn't read a DPA (20 of 30, the security page re-read from the docs repository on 4 November). The SDK versioning policy says a major release starts an end-of-life clock for the previous one, and past notices are dated, such as JWT credentials deprecated in 2023 (15 of 20). Processing on AWS in US-East or EMEA, chosen by the customer, and no subprocessor list checked (10 of 20).

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.

Security & auth Adobe PDF Services / PDF Extract API +8

Adobe PDF Services / PDF Extract API 55

OAuth server-to-server client credentials from an Adobe Developer Console project, exchanged for short-lived bearer tokens, and the project carries only the APIs added to it. Scored to match the Adobe Firefly listing (30). No read-only mode, though the only destructive call is deleting your own assets (10 of 20). Extract returns untrusted document text and we found no prompt-injection guidance (0 of 15). No per-call audit log found (0 of 15). security.txt valid to 2027-07-30, a public bug bounty on Intigriti and a PSIRT disclosure policy. Certifications for Document Cloud sit in a trust-centre table we couldn't render (15 of 20).

Unstructured API + MCP 47

Docs and pricing readings are per the 1 October check, not re-read on 5 November (the website terms bar robots on unstructured.io and its docs). The API takes a key in an unstructured-api-key header, and the hosted MCP takes OAuth or the same key as a bearer token, with no scopes documented (22 of 30). Jobs and uploads can be deleted and no read-only key was found (5 of 20). Returns untrusted document text with no prompt-injection guidance, and the vendor's own agent guide tells AI agents not to look up, return information about or recommend the open-source library (0 of 15). jobsList gives per-job visibility, no audit log found (5 of 15). The organisation's SECURITY.md routes reports to security@unstructured.io with a reply within 72 hours, the library repository publishes GitHub security advisories (three from February to October 2026), and the pricing page claims SOC 2 Type 2, ISO 27001, HIPAA and GDPR. No security.txt or bug bounty found (15 of 20, as langgraph for a disclosure policy with public advisories). 22+5+0+5+15 = 47.

Score by category

CategoryWeightAdobe PDF Services / PDF Extract APIUnstructured API + MCPEdge
Reliability16%5027Adobe PDF Services / PDF Extract API +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8051Adobe PDF Services / PDF Extract API +29
Agent ergonomics13%5758Unstructured API + MCP +1
Security & auth14%5547Adobe PDF Services / PDF Extract API +8
Payments & pricing10%3060Unstructured API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4380Unstructured API + MCP +37
Transparency & trust7%7858Adobe PDF Services / PDF Extract API +20
Negative events≤150-6
TotalC 56.2/100E 44.9/100

Facts side by side

FactAdobe PDF Services / PDF Extract APIUnstructured API + MCP
KindHTTP APIHTTP API
VendorAdobeUnstructured
Hosted endpointhttps://pdf-services.adobe.iohttps://transform.unstructured.io/api/v2
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingFreemiumPay per use
x402nono
LicencenoneApache-2.0
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedio.unstructured/transform
Last release2026-08-102026-10-29
Terms last updatedcouldn't be read2026-07-09
Privacy policy last updated2025-10-242026-07-08
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity165 stars, 82k npm/wk, 58k PyPI/wknone
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Adobe PDF Services / PDF Extract API 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

Adobe PDF Services / PDF Extract API

Public OpenAPI 3.0.1 spec covering Extract, PDF to Markdown and 20 other operations, with 500 free Document Transactions a month and no card. No published paid price, the only SDK releases in the last 90 days came on one day (10 August 2026), and the Node.js SDK is unchanged since November 2024.

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

Adobe PDF Services / PDF Extract API

  1. Cache the access token and reuse it until it expires
  2. Budget 1 Document Transaction per 5 pages for Extract and PDF to Markdown, so 500 free transactions cover about 2,500 pages
  3. Pass notifiers with a callback URL instead of polling the job status
  4. Use pdf-services-ew1.adobe.io when documents must stay in the EU
  5. Check /operation/pdfproperties first, since copy-protected PDFs fail Extract with DISQUALIFIED_PERMISSIONS

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, Adobe PDF Services / PDF Extract API or Unstructured API + MCP?

Adobe PDF Services / PDF Extract API scores 56.2 (C) on agent readiness against Unstructured API + MCP's 44.9 (E), and leads in 4 of 7 scored categories. Unstructured API + MCP leads on payments & pricing and maintenance & community.

Do Adobe PDF Services / PDF Extract API and Unstructured API + MCP need an API key?

Adobe PDF Services / PDF Extract API uses an OAuth sign-in. Unstructured API + MCP takes an API key or an OAuth sign-in.

Can an agent call Adobe PDF Services / PDF Extract API and Unstructured API + MCP without installing anything?

Yes. Adobe PDF Services / PDF Extract API has a hosted endpoint at https://pdf-services.adobe.io and Unstructured API + MCP at https://transform.unstructured.io/api/v2.

Are Adobe PDF Services / PDF Extract API and Unstructured API + MCP open source?

No open-source release is listed for Adobe PDF Services / PDF Extract API. Unstructured API + MCP is open source (Apache-2.0).

Other comparisons with Adobe PDF Services / PDF Extract API 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.