Head to head · PDF conversion · October 2026 research run

Nutrient DWS Processor API vs PDFShift

Nutrient DWS Processor API scores 74.1 (BB) on agent readiness against PDFShift's 66.4 (B), and leads in 6 of 7 scored categories. PDFShift leads on payments & pricing. Both do pdf conversion.

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

Which one, for what

Nutrient DWS Processor API BB

Best for An agent that must change or produce documents (merge, convert, OCR, redact, sign, fill forms) in one chained request with predictable per-use cost, and assistants that want those tools plus extraction through one hosted MCP URL.

Ahead on

  • Reliability, 78 against 73
  • Schema & documentation, 82 against 69
  • Agent ergonomics, 79 against 54
  • Security & auth, 68 against 56
  • Maintenance & community, 83 against 77
  • Transparency & trust, 76 against 67

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

The local MCP server lost support on 14 October 2026, the day the change was announced

PDFShift B

Best for Agents that turn HTML or a live page into a PDF or screenshot in one call, with no browser to run.

Ahead on

  • Payments & pricing, 75 against 60

Also in its favour

  • Free to start without a card

Watch for

Keys come in two levels (master and basic) with no read-only scope, and the MCP server exposes delete_template with no tool annotations

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.

Agent ergonomics Nutrient DWS Processor API +25

Nutrient DWS Processor API 79

API responses are files or json-content with switches for plain text, structured text, key-value pairs and tables. Smithery's copy of the hosted MCP server's tool list shows 14 tools and about 60,000 characters of names, descriptions and input schemas, which we couldn't confirm first-hand. That puts it in the 11 to 30 band with no toolsets or read-only subset, read as openmetadata (16 tools, 49,602 characters) and plane (30 tools, about 67,000) are (15). Page ranges per part and output switches. Nothing to paginate (15). Errors carry failingPaths in JSONPath form, a requestId, and error.reason codes with recommended handling for async jobs (18). Idempotency-Key on async /build only. In Smithery's copy every hosted tool carries readOnlyHint, destructiveHint and idempotentHint, and process_document requires an idempotency_key (17). Single-purpose endpoints such as /processor/generate_pdf need one file, /build chains actions, and official clients exist for TypeScript (3.0.0) and Python (3.1.0) (14). 15+15+18+17+14 = 79.

PDFShift 54

11 compact MCP tools, in the 11 to 30 band; conversions return a download URL rather than the document, which keeps results small (15). list_logs takes limit (5 to 100), status, key and cursor, and conversions take pages; no field selection on other lists (15). Error statuses are documented and the webhook error body carries a code, a message and an identifier, but a missing or malformed key falls back to the free tier with watermarks instead of failing, and the docs disagree on the unauthenticated limits (10 a day on one page, 2 a minute on another) (12). No idempotency key on conversions or template writes, and the MCP tools carry no readOnlyHint or destructiveHint, delete_template included; sandbox mode allows free test runs (4). Only source is required and defaults are sensible; official SDKs exist in Node.js and Python but were last changed in 2019 and 2020 and call /v2 (8). 15 + 15 + 12 + 4 + 8 = 54.

Payments & pricing PDFShift +15

Nutrient DWS Processor API 60

No x402, MPP or L402 (0). Plans are public at $75, $275 and $445 a month for 1,000, 5,000 and 10,000 credits, or $67, $247 and $399 a month billed yearly, and the pricing page gives the credit cost of each tool, from 0.5 for HTML to PDF to 10 for a digital signature (20). The free plan gives 50 Processor credits a month with no card and watermarked output, and the MCP page repeats it (20). The OAuth server supports dynamic client registration and a device flow, but a person still signs in or signs up in a browser, and the hosted MCP server needs the same sign-in (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.

PDFShift 75

No x402, MPP or L402 (0). Plan prices with a per-credit overage for every plan, effective per-document rates and a public pricing endpoint, all without a login (30). Free plan of 50 credits a month with no card, and free watermarked sandbox runs (30). Judgement call on onboarding. The API converts without a key, so an agent can start with no signup, but the output is watermarked, capped at 2 MB and 2 requests a minute; production use needs a browser signup and the key arrives by email (15 of 30). 0 + 30 + 30 + 15 = 75.

Schema & documentation Nutrient DWS Processor API +13

Nutrient DWS Processor API 82

A public OpenAPI 3.1.0 document, now version 1.20.0 per the API reference page, with 17 operations and 203 schemas per the 8 October check of 1.19.0, not re-read on 1 November (25). llms.txt at site and product level with topic indexes, and a Markdown twin of each guide (10). Tag descriptions explain the Build API, async jobs and authorisation at length. The tool descriptions of the hosted MCP server couldn't be read first-hand, since tools/list needs an OAuth token (15, kept from 8 October). 102 of 203 schemas use enums and build actions are discriminated by type, per the 8 October check (13). Guides carry samples in six languages, and the errors guide and async tables document the response bodies (14). The spec is versioned, but the only changelog was the local MCP server's, which stopped with that server on 14 October, and the hosted server 2.0.0 has none. No public API changelog was found, and the move from 1.19.0 to 1.20.0 is undated (5). 25+10+15+13+14+5 = 82.

PDFShift 69

A public OpenAPI 3.0.3 file at api.pdfshift.io/openapi.json, and every MCP tool has a JSON Schema input (25). llms.txt and llms-full.txt on pdfshift.io, llms.txt on the docs, and a Markdown twin of every page (10). MCP descriptions are one line each and say what the tool does, the server's instructions say what it does, and the docs explain the three response shapes; none says when not to use a tool (10). The OpenAPI file has enums (X-Processor-Version), minimum and maximum (zoom) and required fields, and the MCP convert tool has a format enum, but convert and generate_from_template take any further option as free extra properties (9). Request samples in eight languages and 600 guides, an error-code table and a webhook error example with an identifier, though the table's meanings are generic (10). The API is versioned (/v3) and Chromium is pinned by header, but no changelog was found (5). 25 + 10 + 10 + 9 + 10 + 5 = 69.

Security & auth Nutrient DWS Processor API +12

Nutrient DWS Processor API 68

OAuth at api.nutrient.io with PKCE (S256), dynamic client registration, a revocation endpoint and per-product scopes; the hosted MCP server asks for mcp:invoke and accepts product:processor, product:data_extraction and others. Live keys can be scoped, and POST /tokens issues JWTs limited to named operations and origins, expiring within 24 hours and revocable. The base key can only be regenerated. No query-string credential is documented (28). Scoped keys, operation-limited JWTs and product scopes on OAuth, but no confirmation step. The supported MCP route is now hosted and reads no local paths, so the local server's unrestricted file access without SANDBOX_PATH no longer applies (15, up from 13). Document text comes back as untrusted content, and no prompt-injection guidance was found (4). Each response reports credit cost and remaining credits with a request id, a usage endpoint exists, and extraction runs from the MCP server land in a run history the person can review. No audit log was found (6). SOC 2 Type 2 and SOC 3 per the trust centre, annual penetration testing by Prescient Security, and a vulnerability disclosure policy with a report page, per the 8 October check. security.txt is still a 404 and no bounty was established (15). 28+15+4+6+15 = 68.

PDFShift 56

Named keys per account, master or basic, each disabled and re-enabled through the API, with no expiry or finer scopes; the key travels in a header and no query-string option is documented (24). Basic keys can't manage keys, but there is no read-only key, and the MCP server runs delete_template with no annotation or confirmation (6). Results are download URLs, logs and the account's own templates; convert fetches and runs arbitrary pages server-side with no documented guidance on what pages may reach, and generate_from_template can return rendered HTML (8). list_logs and get_log per request, filterable by key, plus last-used time and 7-day usage per key (10). security.txt with a disclosure policy and a 3-business-day response promise, a DPA with technical measures, a HIPAA BAA, but no bug bounty and no SOC 2 or ISO 27001 (pricing asks to be contacted about them) (8). 24 + 6 + 8 + 10 + 8 = 56.

Transparency & trust Nutrient DWS Processor API +9

Nutrient DWS Processor API 76

The API is closed under a dated licence agreement (October 2026) naming PSPDFKit GmbH, and the TypeScript and Python clients are MIT, as is the now unsupported local MCP server, so between the two bands (20). The privacy policy has a Processor API section, the terms carry data processing terms in section 9, and files are deleted within 24 hours on plans without retention. The MCP page says the server keeps nothing, uploads expire after 24 hours, and extraction runs stay in the run history until deleted. Plans with retention enabled let Nutrient keep files and train models on them, and no public page says which plans those are. The October 2026 terms add that free-tier settings apply to Enterprise evaluations unless Nutrient disables retention, and that a paid plan switched to retention needs the customer's acceptance while a free plan needs only advance notice (20). No deprecation policy, and the terms allow changes at any time. The local MCP server's end of support is dated 14 October 2026 in the repository and on npm, with the hosted server named as the replacement, but it took effect the day it was announced (8, up from 4). The trust centre lists 51 sub-processors with locations, updated 8 September 2026, and the status page names Frankfurt and Oregon processing regions, per the 8 October check (18). 20+20+8+18 = 66.

PDFShift 67

Closed service with terms from SASU PDFShift under French law; the SDKs and the n8n node are MIT (15). The FAQ, the DPA's annex and the subprocessors page agree that conversions are held in memory and files kept 2 days on S3 in Paris only with filename or webhook; but the privacy policy dates from 28 February 2022, gives no periods, and lists four services the subprocessors page leaves out, and how long conversion logs are kept isn't stated (20). No deprecation policy or dated notices; Chromium 116 is still selectable alongside 142 (5). Subprocessors and data locations named (OVH Gravelines and Strasbourg, AWS Paris, Sentry) (20). 15 + 20 + 5 + 20 = 60.

Maintenance & community Nutrient DWS Processor API +6

Nutrient DWS Processor API 83

The hosted Nutrient MCP server was published to the official registry as io.nutrient/mcp 2.0.0 on 14 October 2026, still the latest version on 1 November (30). Local MCP releases 0.1.1 and 0.1.2 (24 August) and 0.1.3 (27 August), the TypeScript client 3.0.0 (23 August, per the 17 October check) and the hosted 2.0.0 fall in the 90 days (20). The local server's repository is now reference-only with no further updates or fixes, so its open issues and pull requests won't be answered. For the hosted service there is no public changelog, and support answers through a form with a stated target of one business day (10). io.nutrient/mcp sits in the official registry under Nutrient's own domain namespace (15). The TypeScript and Python clients are current (the Python repository had a commit on 22 October 2026, unreleased), and the deprecated npm package carries a deprecation message pointing to the hosted server (8). 30+20+10+15+8 = 83.

PDFShift 77

Read as a closed service with open-source clients. MCP server 1.0.0 published to the registry on 5 November 2026 (30). n8n node 0.1.2 and 0.1.3 on 8 September 2026, 0.1.4 on 21 September, and the MCP server on 5 November (20). No public changelog; support answers within hours on Business, within 12 hours on other paid plans and within 2 days on Free, per the FAQ; GitHub issue replies weren't read (8 of 15). io.github.cnicodeme/pdfshift in the official registry, a namespace proved through the GitHub account of the managing director named in the imprint (15). The n8n node has CI on pull requests, but the Node.js and Python SDKs were last changed in 2019 and 2020 and target the old /v2 API (4). 30 + 20 + 8 + 15 + 4 = 77.

Score by category

CategoryWeightNutrient DWS Processor APIPDFShiftEdge
Reliability16%7873Nutrient DWS Processor API +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8269Nutrient DWS Processor API +13
Agent ergonomics13%7954Nutrient DWS Processor API +25
Security & auth14%6856Nutrient DWS Processor API +12
Payments & pricing10%6075PDFShift +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8377Nutrient DWS Processor API +6
Transparency & trust7%7667Nutrient DWS Processor API +9
Negative events≤15-10
TotalBB 74.1/100B 66.4/100

Facts side by side

FactNutrient DWS Processor APIPDFShift
KindHTTP APIHTTP API
VendorNutrient (PSPDFKit GmbH)PDFShift
Hosted endpointhttps://api.nutrient.iohttps://api.pdfshift.io/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the Nutrient DWS API licence agreement. The MCP server and the TypeScript and Python clients are MITnone
Tools exposed1411
Read-only variant documentednono
llms.txtyesyes
MCP registryio.nutrient/mcpio.github.cnicodeme/pdfshift
Last release2026-10-142026-11-05
Terms last updated2026-09-01no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textyes
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 textyes
Popularity71 stars, 2.7k npm/wk, 2.2k PyPI/wknone
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Nutrient DWS Processor API

A public OpenAPI 3.1 document, JSONPath-level error bodies and OAuth or operation-limited tokens make the API easy for an agent to call, and 50 free credits a month need no card. The local MCP server lost support the day a hosted one replaced it, and the terms let plans with data retention train models on submitted files.

PDFShift

An agent gets 11 compact MCP tools on a hosted endpoint, a public OpenAPI file, a free plan with no card and free watermarked sandbox runs. Keys are revocable but have only master and basic levels, the MCP tools carry no annotations, and there is no changelog, SLA or current SDK.

Before you call either

Nutrient DWS Processor API

  1. Send Authorization: Bearer <key> to https://api.nutrient.io. Use POST /build with an instructions JSON part to chain several actions in one charged request
  2. Call POST /analyze_build first to get the credit cost of a build. The call is free
  3. Stay under 100 requests a minute per key and back off exponentially on 429. Test keys allow 10 a minute and 5 MB
  4. Use the hosted MCP at https://mcp.nutrient.io/mcp, not @nutrient-sdk/dws-mcp-server, which gets no fixes after 14 October 2026
  5. Ask for a lighter parse mode on simple PDFs. The hosted MCP reads documents in agentic mode by default, at 18 credits a page
  6. Turn on pay-as-you-go or use Processor tools only on a free plan, since free plans include no Data Extraction credits and the hosted MCP reads documents with them

PDFShift

  1. Send the key in the X-API-Key header; a missing or malformed header falls back to the free tier silently, with watermarks and a 2 MB cap
  2. Set sandbox: true while testing; sandbox documents cost no credits and are limited to 10 a minute
  3. Download the file from the returned URL within 2 days; the MCP convert tool and filename responses keep files on S3 for that long only
  4. Check the X-Credits-Cost header and credits_usage before large batches; a credit covers 5 MB, so a 14 MB PDF costs 3
  5. On 429, wait until the X-RateLimit-Reset timestamp; authenticated keys get 250 conversions a minute

Questions

Which is better for AI agents, Nutrient DWS Processor API or PDFShift?

Nutrient DWS Processor API scores 74.1 (BB) on agent readiness against PDFShift's 66.4 (B), and leads in 6 of 7 scored categories. PDFShift leads on payments & pricing.

Do Nutrient DWS Processor API and PDFShift need an API key?

Nutrient DWS Processor API takes an API key or an OAuth sign-in. PDFShift needs an API key.

Can an agent call Nutrient DWS Processor API and PDFShift without installing anything?

Yes. Nutrient DWS Processor API has a hosted endpoint at https://api.nutrient.io and PDFShift at https://api.pdfshift.io/mcp.

Other comparisons with Nutrient DWS Processor API or PDFShift

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.