# iLoveAPI vs Nutrient DWS Processor API

> Nutrient DWS Processor scores 68.7 (B) to iLoveAPI's 42 (E) for pdf conversion. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/iloveapi-vs-nutrient-dws-processor
- Markdown: https://www.anchorterminal.com/compare/iloveapi-vs-nutrient-dws-processor.md (~2,150 tokens)
- Slim: https://www.anchorterminal.com/compare/iloveapi-vs-nutrient-dws-processor.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/iloveapi-vs-nutrient-dws-processor.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 iLoveAPI's 42 (E), and leads in every scored category. Both do pdf conversion.

- iLoveAPI: grade E, 42/100, rank #897 of 950. Markdown https://www.anchorterminal.com/tools/iloveapi.md · JSON https://www.anchorterminal.com/api/v1/tools/iloveapi.json
- Nutrient DWS Processor API: grade B, 68.7/100, rank #209 of 950. Markdown https://www.anchorterminal.com/tools/nutrient-dws-processor.md · JSON https://www.anchorterminal.com/api/v1/tools/nutrient-dws-processor.json
- Best PDF manipulation and conversion APIs for AI agents: https://www.anchorterminal.com/best/pdf-tools/index.md
- All 24 pdf comparisons: https://www.anchorterminal.com/compare/pdf-tools/index.md

## Which one, for what

### iLoveAPI (E)

Good for: An agent that needs common PDF and image operations with a monthly free allowance and a choice of processing region.

Watch for: No OpenAPI file, llms.txt or Markdown docs. The reference is one HTML page

### 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 26
- Schema & documentation, 84 against 37
- Agent ergonomics, 84 against 61
- Security & auth, 66 against 41
- Payments & pricing, 40 against 30
- Maintenance & community, 78 against 62
- Transparency & trust, 73 against 52

Also in its favour:
- Runs on your own machine

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


## Score by category

| Category | Weight | iLoveAPI | Nutrient DWS Processor API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 26 | 68 | Nutrient DWS Processor API +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 37 | 84 | Nutrient DWS Processor API +47 |
| Agent ergonomics | 13% (16.2 this run) | 61 | 84 | Nutrient DWS Processor API +23 |
| Security & auth | 14% (17.5 this run) | 41 | 66 | Nutrient DWS Processor API +25 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Nutrient DWS Processor API +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 62 | 78 | Nutrient DWS Processor API +16 |
| Transparency & trust | 7% (8.8 this run) | 52 | 73 | Nutrient DWS Processor API +21 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **42 · E** | **68.7 · B** | |

## Facts side by side

| Fact | iLoveAPI | Nutrient DWS Processor API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | iLovePDF S.L. | Nutrient (PSPDFKit GmbH) |
| Hosted endpoint | `https://api.ilovepdf.com/v1` | `https://api.nutrient.io` |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the iLovePDF API terms. The client libraries are MIT | Proprietary service under the Nutrient DWS API licence agreement. The MCP server and the TypeScript and Python clients are MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.PSPDFKit/nutrient-dws-mcp-server` |
| Last release | 2026-09-03 | 2026-08-27 |
| Terms last updated | 2017-02-14 | 2026-09-01 |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | not found in the text | yes, with an opt-out |
| 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 | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 9.6k npm/wk | 71 stars, 2.7k npm/wk, 2.2k PyPI/wk |

## Verdicts

**iLoveAPI.** Per-tool credit costs are public, 2,500 free credits arrive each month on a sign-up that asks for no card, and five official libraries are MIT. No OpenAPI file, status page or published rate-limit numbers were found, and the governing terms date from 14 February 2017.

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

## Before you call either

### iLoveAPI

1. Run four calls per job. `GET /v1/start/{tool}/{region}` returns a `server` and a `task`, then send upload, process and download to that server
2. Sign a JWT with the project secret key and send it as `Authorization: Bearer`. Tokens expire after one hour
3. Download results promptly. The reference says files are deleted one to two hours after processing, depending on tier
4. Back off exponentially on 429 and read the rate-limit headers on each response. No limit numbers are published
5. Add `debug=true` to any request to have the server echo the parameters without processing or spending credits

### 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

## Questions

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

Nutrient DWS Processor API scores 68.7 (B) on agent readiness against iLoveAPI's 42 (E), and leads in every scored category.

### Do iLoveAPI and Nutrient DWS Processor API need an API key?

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

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

Yes. iLoveAPI has a hosted endpoint at https://api.ilovepdf.com/v1 and Nutrient DWS Processor API at https://api.nutrient.io.


## For agents

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

## Other comparisons with iLoveAPI or Nutrient DWS Processor API

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