# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co
- Markdown: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co.md (~1,950 tokens)
- Slim: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- Nutrient DWS Processor API: grade B, 68.7/100, rank #197 of 842. Markdown https://www.anchorterminal.com/tools/nutrient-dws-processor.md · JSON https://www.anchorterminal.com/api/v1/tools/nutrient-dws-processor.json
- PDF.co API + MCP: grade F, 37.9/100, rank #817 of 842. Markdown https://www.anchorterminal.com/tools/pdf-co.md · JSON https://www.anchorterminal.com/api/v1/tools/pdf-co.json

## Which one, for what

### Nutrient DWS Processor API (B)

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

### PDF.co API + MCP (F)

Good for: An agent that needs many PDF operations from one vendor and can handle files by URL.

Watch for: No status page. status.pdf.co redirects to betterstack.com/uptime


## Score by category

| Category | Weight | Nutrient DWS Processor API | PDF.co API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 20 | Nutrient DWS Processor API +48 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 74 | Nutrient DWS Processor API +10 |
| Agent ergonomics | 13% (16.2 this run) | 84 | 49 | Nutrient DWS Processor API +35 |
| Security & auth | 14% (17.5 this run) | 66 | 23 | Nutrient DWS Processor API +43 |
| Payments & pricing | 10% (12.5 this run) | 40 | 20 | Nutrient DWS Processor API +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 78 | 34 | Nutrient DWS Processor API +44 |
| Transparency & trust | 7% (8.8 this run) | 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

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. For long jobs send `Prefer: respond-async` with an `Idempotency-Key`, then poll the `Location` URL with `X-Async-Job-Token` after `Retry-After`
5. Set `SANDBOX_PATH` for the MCP server. Without it the server reads and writes any path the user account can reach

### PDF.co API + MCP

1. Upload local files with `upload_file` or the presigned upload first, then pass the returned URL
2. Read the `content` field, not `status`. The MCP server says `working` even when the API returned an error
3. Call `wait_job_completion` after each job. Every MCP call runs async and returns a job id
4. Download results within the hour. Output links expire after 60 minutes by default
5. Keep the key in `X_API_KEY` and leave the `api_key` argument 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdf-co.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "nutrient-dws-processor", "b": "pdf-co"}`. From a terminal: `anchor compare nutrient-dws-processor pdf-co`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nutrient-dws-processor.json and https://www.anchorterminal.com/api/v1/tools/pdf-co.json

## Other comparisons with Nutrient DWS Processor API or PDF.co API + MCP

- [Foxit PDF Services API vs Nutrient DWS Processor API](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-nutrient-dws-processor.md)
- [Foxit PDF Services API vs PDF.co API + MCP](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-pdf-co.md)