# iLoveAPI vs PDFShift (slim)

> PDFShift scores 66.4 (B) to iLoveAPI's 51.8 (D) for pdf conversion. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/iloveapi-vs-pdfshift.md (~4,200 tokens) · this version ~880 tokens · JSON https://www.anchorterminal.com/compare/iloveapi-vs-pdfshift.json · canonical https://www.anchorterminal.com/compare/iloveapi-vs-pdfshift
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

PDFShift scores 66.4 (B) on agent readiness against iLoveAPI's 51.8 (D), and leads in 5 of 7 scored categories. iLoveAPI leads on agent ergonomics. Both do pdf conversion.

- iLoveAPI: D 51.8, rank #1111 of 1563 · https://www.anchorterminal.com/tools/iloveapi.min.md
- PDFShift: B 66.4, rank #490 of 1563 · https://www.anchorterminal.com/tools/pdfshift.min.md
- iLoveAPI, good for An agent that needs common PDF and image operations with a monthly free allowance and a choice of processing region. Ahead on Agent ergonomics, 61 against 54.
- PDFShift, good for Agents that turn HTML or a live page into a PDF or screenshot in one call, with no browser to run. Ahead on Reliability, 73 against 28; Security & auth, 56 against 41; Payments & pricing, 75 against 45; Maintenance & community, 77 against 72. Also Free to start without a card.

| Category | iLoveAPI | PDFShift |
| --- | --- | --- |
| Reliability (16%) | 28 | 73 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 69 |
| Agent ergonomics (13%) | 61 | 54 |
| Security & auth (14%) | 41 | 56 |
| Payments & pricing (10%) | 45 | 75 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 72 | 77 |
| Transparency & trust (7%) | 63 | 67 |

| Fact (where they differ) | iLoveAPI | PDFShift |
| --- | --- | --- |
| Vendor | iLovePDF S.L. | PDFShift |
| Hosted endpoint | `https://api.ilovepdf.com/v1` | `https://api.pdfshift.io/mcp` |
| Transports | HTTP | Streamable HTTP |
| Licence | Proprietary service under the iLovePDF API terms. The client libraries are MIT | none |
| Tools exposed | none | 11 |
| MCP registry | not listed | `io.github.cnicodeme/pdfshift` |
| Terms last updated | 2017-02-14 | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Reliability, PDFShift +45: iLoveAPI 28 (Graded as a hosted API.); PDFShift 73 (Read with the hosted lines.)
- Payments & pricing, PDFShift +30: iLoveAPI 45 (No x402, MPP or L402 (0).); PDFShift 75 (No x402, MPP or L402 (0).)
- Security & auth, PDFShift +15: iLoveAPI 41 (Each project has a public and a secret key.); 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-…)
- Agent ergonomics, iLoveAPI +7: iLoveAPI 61 (Responses are small JSON and output arrives as a file or ZIP, but every job takes four calls and the start call's server must be reused (12).); 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).)
- Maintenance & community, PDFShift +5: iLoveAPI 72 (PHP library v.1.4.2 was tagged on 5 November 2026, fixing how `cloud_file` uploads are sent, 5 days before this check (30).); PDFShift 77 (Read as a closed service with open-source clients.)
