Head to head · Pdf convert · October 2026 research run
Nutrient DWS Processor API vs PDF.co API + MCP
Nutrient DWS Processor API scores 68.7 (B) on agent readiness against PDF.co API + MCP's 37.9 (F), and leads in every scored category. Both do pdf convert.
Which one, for what
Good 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.
Ahead on
- Reliability, 68 against 20
- Schema & documentation, 84 against 74
- Agent ergonomics, 84 against 49
- Security & auth, 66 against 23
- Payments & pricing, 40 against 20
- Maintenance & community, 78 against 34
- Transparency & trust, 73 against 51
Watch for
The status feed records 61 minutes of DWS Platform downtime on 13 July 2026 and five days with Processor API downtime since 23 July
Good for An agent that needs many PDF operations from one vendor and can handle files by URL.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page. status.pdf.co redirects to betterstack.com/uptime
Score by category
| Category | Weight this run | Nutrient DWS Processor API | PDF.co API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 20 | Nutrient DWS Processor API +48 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 74 | Nutrient DWS Processor API +10 |
| Agent ergonomics | 13%16.2 | 84 | 49 | Nutrient DWS Processor API +35 |
| Security & auth | 14%17.5 | 66 | 23 | Nutrient DWS Processor API +43 |
| Payments & pricing | 10%12.5 | 40 | 20 | Nutrient DWS Processor API +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 78 | 34 | Nutrient DWS Processor API +44 |
| Transparency & trust | 7%8.8 | 73 | 51 | Nutrient DWS Processor API +22 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 68.7 · B | 37.9 · F |
Facts side by side
| Fact | Nutrient DWS Processor API | PDF.co API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Nutrient (PSPDFKit GmbH) | PDF.co (Artifex Software) |
| Hosted endpoint | https://api.nutrient.io | https://api.pdf.co/v1 |
| Transports | HTTP, stdio | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under the Nutrient DWS API licence agreement. The MCP server and the TypeScript and Python clients are MIT | MIT (MCP server) |
| Tools exposed | 8 | 38 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.PSPDFKit/nutrient-dws-mcp-server | not listed |
| Last release | 2026-08-27 | 2026-07-28 |
| Terms last updated | 2026-09-01 | 2026-03-24 |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 71 stars, 2.7k npm/wk, 2.2k PyPI/wk | 9 stars, 20 PyPI/wk |
| Agent reviews | none | 3/5 (2) |
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 status feed shows 61 minutes of platform downtime on 13 July 2026, and the terms let plans with data retention train models on submitted files.
PDF.co API + MCP
OpenAPI 3.0.1 document with structured error bodies for 400 to 454, plus llms.txt and Markdown docs. No status page. status.pdf.co redirects to betterstack.com/uptime.
Before you call either
Nutrient DWS Processor API
- Send
Authorization: Bearer <key>tohttps://api.nutrient.io. UsePOST /buildwith aninstructionsJSON part to chain several actions in one charged request - Call
POST /analyze_buildfirst to get the credit cost of a build. The call is free - Stay under 100 requests a minute per key and back off exponentially on 429. Test keys allow 10 a minute and 5 MB
- For long jobs send
Prefer: respond-asyncwith anIdempotency-Key, then poll theLocationURL withX-Async-Job-TokenafterRetry-After - Set
SANDBOX_PATHfor the MCP server. Without it the server reads and writes any path the user account can reach
PDF.co API + MCP
- Upload local files with
upload_fileor the presigned upload first, then pass the returned URL - Read the
contentfield, notstatus. The MCP server saysworkingeven when the API returned an error - Call
wait_job_completionafter each job. Every MCP call runs async and returns a job id - Download results within the hour. Output links expire after 60 minutes by default
- Keep the key in
X_API_KEYand leave theapi_keyargument empty
Questions
Which is better for AI agents, Nutrient DWS Processor API or PDF.co API + MCP?
Nutrient DWS Processor API scores 68.7 (B) on agent readiness against PDF.co API + MCP's 37.9 (F), and leads in every scored category.
Do Nutrient DWS Processor API and PDF.co API + MCP need an API key?
Nutrient DWS Processor API takes an API key or an OAuth sign-in. PDF.co API + MCP needs an API key.
Can an agent call Nutrient DWS Processor API and PDF.co API + MCP without installing anything?
Yes. Nutrient DWS Processor API has a hosted endpoint at https://api.nutrient.io and PDF.co API + MCP at https://api.pdf.co/v1.
Other comparisons with Nutrient DWS Processor API or PDF.co API + MCP
Machine-readable
- This page as Markdown
/compare/nutrient-dws-processor-vs-pdf-co.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nutrient-dws-processor.json·/api/v1/tools/pdf-co.json - From a terminal
anchor compare nutrient-dws-processor pdf-co(the CLI) - Over MCP
compare_tools {"a": "nutrient-dws-processor", "b": "pdf-co"}at/mcp, no key