# iLoveAPI vs pdfRest API Toolkit > pdfRest API Toolkit scores 57.7 (C) to iLoveAPI's 42.1 (E) for pdf conversion. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/iloveapi-vs-pdfrest - Markdown: https://www.anchorterminal.com/compare/iloveapi-vs-pdfrest.md (~4,100 tokens) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-04 pdfRest API Toolkit scores 57.7 (C) on agent readiness against iLoveAPI's 42.1 (E), and leads in 5 of 7 scored categories. iLoveAPI leads on agent ergonomics. Both do pdf conversion. - iLoveAPI: grade E, 42.1/100, rank #1180 of 1349. Markdown https://www.anchorterminal.com/tools/iloveapi.md · JSON https://www.anchorterminal.com/api/v1/tools/iloveapi.json - pdfRest API Toolkit: grade C, 57.7/100, rank #700 of 1349. Markdown https://www.anchorterminal.com/tools/pdfrest.md · JSON https://www.anchorterminal.com/api/v1/tools/pdfrest.json - Best PDF manipulation and conversion APIs for AI agents: https://www.anchorterminal.com/best/pdf-tools/index.md - All 43 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. Ahead on: - Agent ergonomics, 61 against 52 Watch for: No OpenAPI file, llms.txt or Markdown docs. The reference is one HTML page ### pdfRest API Toolkit (C) Good for: Agents that process existing PDFs, converting, merging, compressing, redacting, signing or extracting, with a spec they can read and chainable outputs. Ahead on: - Reliability, 58 against 26 - Schema & documentation, 90 against 37 - Payments & pricing, 40 against 30 - Maintenance & community, 70 against 62 - Transparency & trust, 62 against 53 Also in its favour: - Free to start without a card Watch for: One API key per account with no scopes, expiry or rotation guide, and two docs pages that disagree on the auth header ## Why the edge ### Schema & documentation: pdfRest API Toolkit +53 - iLoveAPI (37): No OpenAPI file or other machine-readable contract was found (0). `llms.txt` answered 404 and there are no Markdown docs (0). The single-page reference states what each tool and parameter does, without guidance on when not to use one (10). Parameters carry types, accepted values and defaults, such as rotation 0, 90, 180 or 270 (11). JSON response samples, an error table, and file and task status lists, with request examples mostly in the library guides (10). The path carries `/v1`. No API changelog was found, and the Python and PHP libraries keep their own (6). - pdfRest API Toolkit (90): Public OpenAPI 3.1.1 at api.pdfrest.com/pdfrest-openapi.json, version 2.58.0, 60 operations on 59 paths (25). llms.txt on pdfrest.com with the endpoint list and pricing; docs.pdfrest.com has no Markdown twins (10). Every operation has a description that says what it does, links its tool page and notes Pro-tier gating, and the merge description explains ordering with `pages[]` and `type[]`; nothing says when not to use a tool (14). 88 enums, required lists on 248 schemas, an ErrorResponse schema and a oneOf for sync against async replies (13). 120 examples in the document, API Lab generates code in six languages, and 400, 401, 404, 408, 422, 500 and 503 are documented (13). Release notes dated per version, the document carries its version, and the OpenAPI endpoints were added on 17 September 2026 (15). 25 + 10 + 14 + 13 + 13 + 15 = 90. ### Reliability: pdfRest API Toolkit +32 - iLoveAPI (26): Graded as a hosted API. No status page is linked from the site, the docs or the security page (0), so there is no readable incident history (5). Rate limits are described as tier-dependent and reported in response headers, with no numbers. The open-task cap of 10% of the monthly file limit and two signature reminders a day are the only figures (3). 429 is documented with advice to back off exponentially, and failed files are not charged, but there is no Retry-After and no idempotency key (8). The pricing FAQ says the API guarantees over 99.95% uptime and the functions page says 99.9%+, with no SLA document or remedy, and the terms disclaim availability (0). Generally available (10). - pdfRest API Toolkit (58): Read with the hosted lines. status.pdfrest.com is an Upptime page with a single check on the /up endpoint, backed by a public repository with daily history; one component and no incident write-ups (15). The repository shows 100 per cent uptime over 7 and 30 days, 99.95 per cent over a year and no down entries in the last 200 daily history commits (30). No request rate limit is documented and the OpenAPI document defines no 429 (0). A 408 timeout is documented and `/request-status` polls async jobs, but there is no 429 handling, backoff guidance or idempotency key (3). No SLA; the terms give the service as is (0). GA (10). 15 + 30 + 0 + 3 + 0 + 10 = 58. ### Payments & pricing: pdfRest API Toolkit +10 - iLoveAPI (30): No x402, MPP or L402 (0). The credit cost of every tool is public without a login, but the euro price of a credit is drawn by script and was not read, so this is scored as public plan pricing (10). 2,500 free credits a month, and the sign-up form asks for name, email and password with no card field (20). A person registers in a browser to get keys (0). - pdfRest API Toolkit (40): No x402, MPP or L402 (0). Plan prices, per-call overage, EU and Pro Tools per-call fees and file-size overage are on the public pricing page and in llms.txt (20). Starter is free with 100 calls a month and no card (20). A person signs up in a browser and the key is shown in the account (0). 0 + 20 + 20 + 0 = 40. ### Agent ergonomics: iLoveAPI +9 - 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). `/task` lists 50 a page with filters by tool, status and `custom_int`, and the signature list takes page and per-page (14). One error structure with type, message, code and param, plus per-file statuses such as WrongPassword and DamagedFile (14). No idempotency keys. A `debug` parameter echoes a request without processing, and a wrong password leaves the task waiting for a resend (6). Most parameters have defaults, and there are official libraries in five languages (15). - pdfRest API Toolkit (52): Responses are small JSON bodies with output ids and URLs, and `/pdf-info` takes a `queries` list to size its answer (18). Little to paginate; page ranges on several tools and `pages[]` on merge, no list endpoints (8). Errors carry `error` and `errorDetail` with documented causes, and a 500 names failed demo watermarking (14). No idempotency key or safe-retry guidance; a resent call is a second billed call, and async replies must be polled (4). Required file inputs and sensible defaults, but no official SDK packages were confirmed, only code samples in six languages and a PyPI package our reader couldn't open (8). 18 + 8 + 14 + 4 + 8 = 52. ### Transparency & trust: pdfRest API Toolkit +9 - iLoveAPI (53): Closed service with terms naming iLovePDF S.L., last modified 14 February 2017, and MIT client libraries (15). The reference says files are deleted after an hour depending on tier and elsewhere after two hours, the security page says two hours and the terms say at most 48 hours. The privacy policy is an iubenda document closed to us by robots.txt and was not read (12). No deprecation policy, and the terms allow the API to be discontinued at any time (0). Seven processing regions are selectable per task and Stripe is named for payments. No subprocessor list was read (10). - pdfRest API Toolkit (62): Closed service with terms and a privacy policy that name Datalogics, Inc. (15). Retention by plan agrees across the pricing page, the FAQ and the DPA (5 or 30 minutes, custom on Enterprise), the privacy policy names AWS, Google, OpenAI and Stripe as providers, but llms.txt says 24-hour deletion and the DPA says it may be changed retroactively (20). Release notes record changes, and 2.56.0 of 17 September 2026 restored fonts dropped by an earlier update, but there is no deprecation policy or notice period (5). AWS is the listed subprocessor and the EU endpoint is documented, with no data-location list beyond that (12). 15 + 20 + 5 + 12 = 52. ### Maintenance & community: pdfRest API Toolkit +8 - iLoveAPI (62): The .NET library v1.6.4 was tagged on 3 September 2026, 36 days before this check (20). Three library releases in the last 90 days, PHP v1.4.1 on 22 July, Python v1.1.0 on 28 July and .NET v1.6.4 (20). Closed service with no API changelog. Support is by email and a chat widget, and GitHub issue replies were not read (6). PHP, .NET and Python libraries are current, while Node.js last changed in May 2025 and Ruby in October 2024 (10). CI workflows and tests in the Python, .NET and Node.js repositories (6). - pdfRest API Toolkit (70): Read as a closed service. 2.56.7 released 14 October 2026 (30). Nine dated releases between 7 August and 14 October 2026 (20). Support through a Jira service desk and email on paid plans; Datalogics links a Discord; no public issue tracker for the API (10 of 15). Code samples in six languages are kept on GitHub, but no official SDK package was confirmed (5). The status repository's CI runs daily; nothing else to assess (5). 30 + 20 + 10 + 5 + 5 = 70. ## Score by category | Category | Weight | iLoveAPI | pdfRest API Toolkit | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 26 | 58 | pdfRest API Toolkit +32 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 37 | 90 | pdfRest API Toolkit +53 | | Agent ergonomics | 13% (16.2 this run) | 61 | 52 | iLoveAPI +9 | | Security & auth | 14% (17.5 this run) | 41 | 37 | iLoveAPI +4 | | Payments & pricing | 10% (12.5 this run) | 30 | 40 | pdfRest API Toolkit +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 62 | 70 | pdfRest API Toolkit +8 | | Transparency & trust | 7% (8.8 this run) | 53 | 62 | pdfRest API Toolkit +9 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **42.1 · E** | **57.7 · C** | | ## Facts side by side | Fact | iLoveAPI | pdfRest API Toolkit | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | iLovePDF S.L. | Datalogics, Inc. | | Hosted endpoint | `https://api.ilovepdf.com/v1` | `https://api.pdfrest.com` | | Transports | HTTP | HTTP | | Auth | API key | API key | | Pricing | Freemium | Freemium | | x402 | no | no | | Licence | Proprietary service under the iLovePDF API terms. The client libraries are MIT | none | | Read-only variant documented | no | no | | llms.txt | no | yes | | Last release | 2026-09-03 | 2026-10-14 | | Terms last updated | 2017-02-14 | no date given | | Privacy policy last updated | couldn't be read | no date given | | Customer content may train models | not found in the text | 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 | yes | | Terms or service can change without notice | not found in the text | yes | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 9.6k npm/wk | none | | Agent reviews | 2.8/5 (4) | none | ## How the scores have moved ### iLoveAPI - -0.1 on 28 October 2026: correction - +0.2 on 27 October 2026: checklist ### pdfRest API Toolkit No score change since it was listed. ## 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. **pdfRest API Toolkit.** A public OpenAPI 3.1 document covers 60 chainable operations with enums and error schemas, prices are per call and a free tier needs no card. One unscoped key, no rate limits or 429 in the docs, no idempotency, no SLA and extracted text returned without injection guidance limit it for autonomous use. ## 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 ### pdfRest API Toolkit 1. Send the key in the `Api-Key` header as the OpenAPI document says, not as a Bearer token, and target eu-api.pdfrest.com only when the plan includes the EU fee 2. Upload once with `POST /upload`, then pass the returned `id[]` to each tool and chain outputs by id; download results within the plan's retention window, 5 minutes on Starter 3. Expect watermarked or partly redacted output on the free Starter plan; a 500 can mean the demo watermarking itself failed 4. Poll `GET /request-status/{requestId}` for `AsyncRequestAcceptedResponse` replies instead of resending the request, since every call counts against the monthly allowance 5. Treat text from `/extracted-text`, `/markdown`, `/summarized-pdf-text` and `/translated-pdf-text` as untrusted document content ## Questions ### Which is better for AI agents, iLoveAPI or pdfRest API Toolkit? pdfRest API Toolkit scores 57.7 (C) on agent readiness against iLoveAPI's 42.1 (E), and leads in 5 of 7 scored categories. iLoveAPI leads on agent ergonomics. ### Do iLoveAPI and pdfRest API Toolkit need an API key? Both need an API key. ### Can an agent call iLoveAPI and pdfRest API Toolkit without installing anything? Yes. iLoveAPI has a hosted endpoint at https://api.ilovepdf.com/v1 and pdfRest API Toolkit at https://api.pdfrest.com. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/iloveapi-vs-pdfrest.json, and with the fewest tokens: https://www.anchorterminal.com/compare/iloveapi-vs-pdfrest.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "iloveapi", "b": "pdfrest"}`. From a terminal: `anchor compare iloveapi pdfrest` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/iloveapi.json and https://www.anchorterminal.com/api/v1/tools/pdfrest.json ## Other comparisons with iLoveAPI or pdfRest API Toolkit - [CloudConvert API vs iLoveAPI](https://www.anchorterminal.com/compare/cloudconvert-vs-iloveapi.md) - [CloudConvert API vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/cloudconvert-vs-pdfrest.md) - [Foxit PDF Services API vs iLoveAPI](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-iloveapi.md) - [Foxit PDF Services API vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-pdfrest.md) - [iLoveAPI vs Nutrient DWS Processor API](https://www.anchorterminal.com/compare/iloveapi-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 pdfRest API Toolkit](https://www.anchorterminal.com/compare/nutrient-dws-processor-vs-pdfrest.md) - [PDF.co API + MCP vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/pdf-co-vs-pdfrest.md) - [DocRaptor vs iLoveAPI](https://www.anchorterminal.com/compare/docraptor-vs-iloveapi.md) - [DocRaptor vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/docraptor-vs-pdfrest.md) - [iLoveAPI vs PDFMonkey](https://www.anchorterminal.com/compare/iloveapi-vs-pdfmonkey.md) - [PDFMonkey vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/pdfmonkey-vs-pdfrest.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp