Head to head · PDF conversion · October 2026 research run

iLoveAPI vs PDFShift

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.

Best PDF manipulation and conversion APIs for AI agents · All 67 pdf comparisons

Which one, for what

iLoveAPI D

Best 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

Watch for

No status page is linked from the site or docs, and rate limits are described as tier-dependent with no numbers

PDFShift B

Best 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 in its favour

  • Free to start without a card

Watch for

Keys come in two levels (master and basic) with no read-only scope, and the MCP server exposes delete_template with no tool annotations

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability PDFShift +45

iLoveAPI 28

Graded as a hosted API. No status page is linked from the site, the docs, llms.txt or the legal pages (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 is the only figure (3, held as a partial). The reference documents 429 and recommends exponential backoff, with no Retry-After and no idempotency key; backoff guidance alone is this run's 10 (8 on 9 October wasn't a checklist value). The pricing page now says the API guarantees over 99.999% uptime, with no SLA document or remedy, and the terms disclaim availability (0). Generally available (10). Re-read on 10 November. 0 + 5 + 3 + 10 + 0 + 10 = 28.

PDFShift 73

Read with the hosted lines. status.pdfshift.io is a Better Stack page with eight monitors (API and two processors in each of Gravelines and Strasbourg, the website and the dashboard) (20). Its incident list shows no incidents from September to November 2026, but the Strasbourg API monitor shows 99.660 per cent uptime, over a window the page doesn't state, so downtime went without a write-up; read as minor incidents only (20). Rate limits with numbers: 250 conversions a minute authenticated, 10 a minute in sandbox, 2 a minute without a key, 50 parallel conversions (15). 429 is documented with X-RateLimit-Remaining, X-RateLimit-Limit and X-RateLimit-Reset, but no Retry-After, backoff advice or idempotency guidance (8). No SLA on any listed plan; the home page mentions one only for custom Enterprise plans (0). GA (10). 20 + 20 + 15 + 8 + 0 + 10 = 73.

Payments & pricing PDFShift +30

iLoveAPI 45

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 still drawn by script and was not read, so this is scored as public plan pricing (10). 2,500 free credits a month for every non-AI PDF and image tool, with no card field on the sign-up form per the 9 October check (20). A person registers in a browser to get keys (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

PDFShift 75

No x402, MPP or L402 (0). Plan prices with a per-credit overage for every plan, effective per-document rates and a public pricing endpoint, all without a login (30). Free plan of 50 credits a month with no card, and free watermarked sandbox runs (30). Judgement call on onboarding. The API converts without a key, so an agent can start with no signup, but the output is watermarked, capped at 2 MB and 2 requests a minute; production use needs a browser signup and the key arrives by email (15 of 30). 0 + 30 + 30 + 15 = 75.

Security & auth PDFShift +15

iLoveAPI 41

Each project has a public and a secret key. Requests carry either the secret key in an X-Api-Key header, which the reference says is never read from the URL or body, or a JWT signed with the secret that expires after one hour. Domain and IP filters exist depending on tier. No scopes, and a leaked key is replaced by deleting the project (20). No read-only key or confirmation before a task is deleted, and /auth issues a token for the public key alone unless a domain filter is set (4). OCR, Markdown and summary output is untrusted text and the docs give no injection guidance (0). /task lists processed tasks and signatures have a downloadable audit trail, with no account audit log found (7). ISO/IEC 27001:2022 certificate linked from the security page, re-read on 10 November. No disclosure policy or bounty was found, and security.txt answered 403 on 9 October (10). 20 + 4 + 0 + 7 + 10 = 41.

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-string option is documented (24). Basic keys can't manage keys, but there is no read-only key, and the MCP server runs delete_template with no annotation or confirmation (6). Results are download URLs, logs and the account's own templates; convert fetches and runs arbitrary pages server-side with no documented guidance on what pages may reach, and generate_from_template can return rendered HTML (8). list_logs and get_log per request, filterable by key, plus last-used time and 7-day usage per key (10). security.txt with a disclosure policy and a 3-business-day response promise, a DPA with technical measures, a HIPAA BAA, but no bug bounty and no SOC 2 or ISO 27001 (pricing asks to be contacted about them) (8). 24 + 6 + 8 + 10 + 8 = 56.

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). /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, an X-Api-Key header now skips token signing, and there are official libraries in five languages (15). Re-read on 10 November. 12 + 14 + 14 + 6 + 15 = 61.

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). list_logs takes limit (5 to 100), status, key and cursor, and conversions take pages; no field selection on other lists (15). Error statuses are documented and the webhook error body carries a code, a message and an identifier, but a missing or malformed key falls back to the free tier with watermarks instead of failing, and the docs disagree on the unauthenticated limits (10 a day on one page, 2 a minute on another) (12). No idempotency key on conversions or template writes, and the MCP tools carry no readOnlyHint or destructiveHint, delete_template included; sandbox mode allows free test runs (4). Only source is required and defaults are sensible; official SDKs exist in Node.js and Python but were last changed in 2019 and 2020 and call /v2 (8). 15 + 15 + 12 + 4 + 8 = 54.

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). Three library releases in the 90 days from 12 August, .NET v1.6.4 (3 September, AI tools), .NET v1.6.5 (27 October, a JWT claim fix) and PHP v.1.4.2, each changing library code (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). 30 + 20 + 6 + 10 + 6 = 72.

PDFShift 77

Read as a closed service with open-source clients. MCP server 1.0.0 published to the registry on 5 November 2026 (30). n8n node 0.1.2 and 0.1.3 on 8 September 2026, 0.1.4 on 21 September, and the MCP server on 5 November (20). No public changelog; support answers within hours on Business, within 12 hours on other paid plans and within 2 days on Free, per the FAQ; GitHub issue replies weren't read (8 of 15). io.github.cnicodeme/pdfshift in the official registry, a namespace proved through the GitHub account of the managing director named in the imprint (15). The n8n node has CI on pull requests, but the Node.js and Python SDKs were last changed in 2019 and 2020 and target the old /v2 API (4). 30 + 20 + 8 + 15 + 4 = 77.

Score by category

CategoryWeightiLoveAPIPDFShiftEdge
Reliability16%2873PDFShift +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7269iLoveAPI +3
Agent ergonomics13%6154iLoveAPI +7
Security & auth14%4156PDFShift +15
Payments & pricing10%4575PDFShift +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7277PDFShift +5
Transparency & trust7%6367PDFShift +4
Negative events≤1500
TotalD 51.8/100B 66.4/100

Facts side by side

FactiLoveAPIPDFShift
KindHTTP APIHTTP API
VendoriLovePDF S.L.PDFShift
Hosted endpointhttps://api.ilovepdf.com/v1https://api.pdfshift.io/mcp
TransportsHTTPStreamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the iLovePDF API terms. The client libraries are MITnone
Tools exposednone11
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.cnicodeme/pdfshift
Last release2026-11-052026-11-05
Terms last updated2017-02-14no date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Agent reviews2.8/5 (4)none

How the scores have moved

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 an OpenAPI 3.1 file, llms.txt and five MIT libraries are published. No status page or rate-limit numbers were found, and retention is stated as two hours in one document and 48 in another.

PDFShift

An agent gets 11 compact MCP tools on a hosted endpoint, a public OpenAPI file, a free plan with no card and free watermarked sandbox runs. Keys are revocable but have only master and basic levels, the MCP tools carry no annotations, and there is no changelog, SLA or current SDK.

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. Send the project secret key in X-Api-Key from server code, or a JWT signed with 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. Read https://www.iloveapi.com/docs/api-reference.md for the full reference in Markdown

PDFShift

  1. Send the key in the X-API-Key header; a missing or malformed header falls back to the free tier silently, with watermarks and a 2 MB cap
  2. Set sandbox: true while testing; sandbox documents cost no credits and are limited to 10 a minute
  3. Download the file from the returned URL within 2 days; the MCP convert tool and filename responses keep files on S3 for that long only
  4. Check the X-Credits-Cost header and credits_usage before large batches; a credit covers 5 MB, so a 14 MB PDF costs 3
  5. On 429, wait until the X-RateLimit-Reset timestamp; authenticated keys get 250 conversions a minute

Questions

Which is better for AI agents, iLoveAPI or PDFShift?

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.

Do iLoveAPI and PDFShift need an API key?

Both need an API key.

Can an agent call iLoveAPI and PDFShift without installing anything?

Yes. iLoveAPI has a hosted endpoint at https://api.ilovepdf.com/v1 and PDFShift at https://api.pdfshift.io/mcp.

Other comparisons with iLoveAPI or PDFShift

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.