Head to head · PDF conversion · October 2026 research run

pdfRest API Toolkit vs PDFShift

PDFShift scores 66.4 (B) on agent readiness against pdfRest API Toolkit's 60.2 (C), and leads in 6 of 7 scored categories. pdfRest API Toolkit leads on schema & documentation. Both do pdf conversion.

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

Which one, for what

pdfRest API Toolkit C

Best for Agents that process existing PDFs, converting, merging, compressing, redacting, signing or extracting, with a spec they can read and chainable outputs.

Ahead on

  • Schema & documentation, 90 against 69

Watch for

One API key per account with no scopes, expiry or rotation guide, and two docs pages that disagree on the auth header

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 58
  • Security & auth, 56 against 37
  • Payments & pricing, 75 against 60
  • Maintenance & community, 77 against 70
  • Transparency & trust, 67 against 62

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.

Schema & documentation pdfRest API Toolkit +21

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.

PDFShift 69

A public OpenAPI 3.0.3 file at api.pdfshift.io/openapi.json, and every MCP tool has a JSON Schema input (25). llms.txt and llms-full.txt on pdfshift.io, llms.txt on the docs, and a Markdown twin of every page (10). MCP descriptions are one line each and say what the tool does, the server's instructions say what it does, and the docs explain the three response shapes; none says when not to use a tool (10). The OpenAPI file has enums (X-Processor-Version), minimum and maximum (zoom) and required fields, and the MCP convert tool has a format enum, but convert and generate_from_template take any further option as free extra properties (9). Request samples in eight languages and 600 guides, an error-code table and a webhook error example with an identifier, though the table's meanings are generic (10). The API is versioned (/v3) and Chromium is pinned by header, but no changelog was found (5). 25 + 10 + 10 + 9 + 10 + 5 = 69.

Security & auth PDFShift +19

pdfRest API Toolkit 37

One Api-Key header per account, revocable per the terms, with no scopes, expiry or rotation guide, and the polling guide shows a Bearer header instead (14). No read-only key; /delete removes uploaded files and there is no confirmation step, though demo output is watermarked (4). Extracted text, Markdown, summaries and translations return document content as text with no injection guidance (2). The container edition logs audit events; nothing documents per-call visibility for cloud accounts beyond usage counts (5). SOC 2 Type 2 through Datalogics' trust centre, HIPAA BAAs and a DPA, but no security.txt, disclosure policy or bug bounty found (12). 14 + 4 + 2 + 5 + 12 = 37.

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.

Reliability PDFShift +15

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.

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 +15

pdfRest API Toolkit 60

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Maintenance & community PDFShift +7

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.

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.

Transparency & trust PDFShift +5

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.

PDFShift 67

Closed service with terms from SASU PDFShift under French law; the SDKs and the n8n node are MIT (15). The FAQ, the DPA's annex and the subprocessors page agree that conversions are held in memory and files kept 2 days on S3 in Paris only with filename or webhook; but the privacy policy dates from 28 February 2022, gives no periods, and lists four services the subprocessors page leaves out, and how long conversion logs are kept isn't stated (20). No deprecation policy or dated notices; Chromium 116 is still selectable alongside 142 (5). Subprocessors and data locations named (OVH Gravelines and Strasbourg, AWS Paris, Sentry) (20). 15 + 20 + 5 + 20 = 60.

Score by category

CategoryWeightpdfRest API ToolkitPDFShiftEdge
Reliability16%5873PDFShift +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9069pdfRest API Toolkit +21
Agent ergonomics13%5254PDFShift +2
Security & auth14%3756PDFShift +19
Payments & pricing10%6075PDFShift +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7077PDFShift +7
Transparency & trust7%6267PDFShift +5
Negative events≤1500
TotalC 60.2/100B 66.4/100

Facts side by side

FactpdfRest API ToolkitPDFShift
KindHTTP APIHTTP API
VendorDatalogics, Inc.PDFShift
Hosted endpointhttps://api.pdfrest.comhttps://api.pdfshift.io/mcp
TransportsHTTPStreamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
Tools exposednone11
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.cnicodeme/pdfshift
Last release2026-10-142026-11-05
Terms last updatedno date givenno date given
Privacy policy last updatedno date givenno 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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes

How the scores have moved

Verdicts

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.

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

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

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, pdfRest API Toolkit or PDFShift?

PDFShift scores 66.4 (B) on agent readiness against pdfRest API Toolkit's 60.2 (C), and leads in 6 of 7 scored categories. pdfRest API Toolkit leads on schema & documentation.

Do pdfRest API Toolkit and PDFShift need an API key?

Both need an API key.

Can an agent call pdfRest API Toolkit and PDFShift without installing anything?

Yes. pdfRest API Toolkit has a hosted endpoint at https://api.pdfrest.com and PDFShift at https://api.pdfshift.io/mcp.

Other comparisons with pdfRest API Toolkit 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.