Head to head · Document extraction · October 2026 research run

Adobe PDF Services / PDF Extract API vs Invofox

Adobe PDF Services / PDF Extract API scores 56.2 (C) on agent readiness against Invofox's 47 (D), and leads in 5 of 7 scored categories. Invofox leads on agent ergonomics and payments & pricing. Both do document extraction.

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

Best PDF manipulation and conversion APIs for AI agents · All 67 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 25
  • Schema & documentation, 80 against 70
  • Security & auth, 55 against 45
  • Maintenance & community, 43 against 20
  • Transparency & trust, 78 against 57

Watch for

No published paid price, paid use goes through sales

Invofox D

Best for Teams that process a known set of business documents (invoices, payslips, bank statements, mortgage forms) at volume and can receive webhooks.

Ahead on

  • Agent ergonomics, 64 against 57
  • Payments & pricing, 45 against 30

Watch for

No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one (5 November)

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 Adobe PDF Services / PDF Extract API +25

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.

Invofox 25

No public status page found. status.invofox.com still doesn't resolve on 5 November and neither the site nor the docs link to one (0 of 20). No readable incident history (5 of 30). No rate limit numbers, and the vendor's AI briefing still says rate limits are not publicly documented (0 of 15). The main OpenAPI file documents 429 with RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers, and the docs ask for exponential backoff, but uploads take no idempotency key (10 of 15). The pricing page lists a 99.9% uptime SLA on Starter, but no SLA document was found, and this run scores a pricing-page SLA figure with no document 0 (0 of 10). The API is in production use and self-serve since 5 October 2026 (10). 0 + 5 + 0 + 10 + 0 + 10 = 25.

Maintenance & community Adobe PDF Services / PDF Extract API +23

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.

Invofox 20

No changelog or versioned release of the API was found. The self-serve launch on 5 October 2026 opened sign-up and API keys to new users but changed no documented API behaviour, and a service start isn't a recency source in this run; the docs sitemap date of 7 October 2026 records no change. No dated API change was found on the docs, the site's llms.txt or the blog, whose newest post is from 7 August 2026. The vendor's newest dated release is its n8n community node n8n-nodes-invofox 0.1.0, tagged on 3 July 2026, 125 days before 5 November (10). No three dated releases in the last 90 days (0). Community support on Free and email support on Starter, replies not sampled, no public changelog (3 of 15). No official SDK, and the n8n node is the vendor's only package (3 of 15). That repository has CI and publish workflows and no commit since 3 July (4 of 10). 10 + 0 + 3 + 3 + 4 = 20.

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

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

Invofox 57

Closed service. The published terms are a website legal notice, and the General Terms and Conditions that the DPA cites were not found on the site. The DPA and NDA are public (12 of 30). The zero-retention page says the standard pipeline keeps documents and that real documents tune the model, with no default retention period stated. Zero retention is opt-in for Scale and Enterprise. The DPA allows three months of access after termination and gives 48 hours for breach notice (15 of 30). Five operations and several fields are marked deprecated in the OpenAPI files with replacements named and no removal dates (5 of 20). The DPA points to a sub-processor list in the trust centre, which we could not read, with 15 days' notice of changes. The site states EU and US processing regions (8 of 20).

Payments & pricing Invofox +15

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.

Invofox 45

No x402, MPP or L402 (0). Plan prices are public, Free at $0 for 500 pages and Starter from $500 a month billed annually for up to 5,000 pages, but no per-page or overage rate is published and Scale and Enterprise are custom (10 of 20). The free plan needs no card (20). A person signs up in a browser at app.invofox.com and creates the key in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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

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

Invofox 70

Three public OpenAPI 3.1 files, main (25 operations), ingest (7) and webhooks (7 events) (25). llms.txt on both the site and the docs, and every docs page has a Markdown twin (10). The guides say when to use webhooks or polling and how rejected files behave, but 11 of the 25 main operations have no description (12 of 20). States, confidence and error codes are enums and limit has a maximum of 500, while info is a JSON string inside multipart and filter is a JSON string in the query (9 of 15). Examples in curl, Python and Node.js and tables of error codes, with inconsistencies. A sample shows ERR_PASSWORD_PROTECTED, which is missing from the code table, the main file's error text says 50 MB and 10 pages where the ingest file says 100 MB, and webhook samples show version 1.0 and 1.2 (9 of 15). Ingest paths carry /v1 and webhook events a version field, and no public changelog was found (5 of 15).

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

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

Invofox 45

API keys in an x-api-key header, created in the dashboard and scoped to one environment, which is either TEST or PRODUCTION. Revocation and rotation are not described in the docs we read (20 of 30). Environment scoping is the only least-privilege control found. The same key reaches the delete endpoints for users, companies, providers and clients, with no read-only key or confirmation (6 of 20). The API returns text taken from untrusted documents and no prompt-injection guidance was found (0 of 15). Document and import lists record channel and creator, and no audit log is documented (5 of 15). security.txt is valid until 1 June 2027 with security@invofox.com. The site states SOC 2 Type II, ISO 27001:2022, GDPR and HIPAA compliance and links a Vanta trust centre we could not read without JavaScript. No bug bounty found (14 of 20).

Score by category

CategoryWeightAdobe PDF Services / PDF Extract APIInvofoxEdge
Reliability16%5025Adobe PDF Services / PDF Extract API +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8070Adobe PDF Services / PDF Extract API +10
Agent ergonomics13%5764Invofox +7
Security & auth14%5545Adobe PDF Services / PDF Extract API +10
Payments & pricing10%3045Invofox +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4320Adobe PDF Services / PDF Extract API +23
Transparency & trust7%7857Adobe PDF Services / PDF Extract API +21
Negative events≤1500
TotalC 56.2/100D 47/100

Facts side by side

FactAdobe PDF Services / PDF Extract APIInvofox
KindHTTP APIHTTP API
VendorAdobeInvofox, Inc.
Hosted endpointhttps://pdf-services.adobe.iohttps://api.invofox.com
TransportsHTTPHTTP
AuthOAuthAPI key
PricingFreemiumFreemium
x402nono
LicencenoneProprietary hosted service. The n8n community node on GitHub is MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-102026-07-03
Terms last updatedcouldn't be readno date given
Privacy policy last updated2025-10-24no date given
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)3.3/5 (4)

The panel on both

One of the 2 reviewers who reviewed both rates Invofox higher, the other way from the total score.

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.

Invofox

Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise.

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

Invofox

  1. Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types
  2. Upload with POST /v1/ingest/uploads as multipart, with info as a JSON string. Send "useClassifier": true in place of type to have the type detected
  3. Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded
  4. Handle the file.rejected webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely
  5. Do not retry an upload blindly. There is no idempotency key, so send your own id in clientData and look it up with filter first

Questions

Which is better for AI agents, Adobe PDF Services / PDF Extract API or Invofox?

Adobe PDF Services / PDF Extract API scores 56.2 (C) on agent readiness against Invofox's 47 (D), and leads in 5 of 7 scored categories. Invofox leads on agent ergonomics and payments & pricing.

Do Adobe PDF Services / PDF Extract API and Invofox need an API key?

Adobe PDF Services / PDF Extract API uses an OAuth sign-in. Invofox needs an API key.

Can an agent call Adobe PDF Services / PDF Extract API and Invofox without installing anything?

Yes. Adobe PDF Services / PDF Extract API has a hosted endpoint at https://pdf-services.adobe.io and Invofox at https://api.invofox.com.

Other comparisons with Adobe PDF Services / PDF Extract API or Invofox

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.