Head to head · PDF conversion · October 2026 research run

CloudConvert API vs PDFShift

PDFShift and CloudConvert API score within a point of each other on agent readiness, 66.4 (B) and 66.2 (B). CloudConvert API leads on reliability, agent ergonomics, security & auth and transparency & trust. Both do pdf conversion.

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

Which one, for what

CloudConvert API B

Best for An agent that converts between many file formats, merges to PDF, or needs OCR, PDF/A, encryption and page operations in one job, with storage on S3, Azure or Google Cloud.

Ahead on

  • Reliability, 80 against 73
  • Agent ergonomics, 61 against 54
  • Security & auth, 71 against 56
  • Transparency & trust, 75 against 67

Watch for

No OpenAPI document and no API changelog were found. The blog has one post since August 2024

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

  • Schema & documentation, 69 against 59
  • Payments & pricing, 75 against 53
  • Maintenance & community, 77 against 58

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.

Payments & pricing PDFShift +22

CloudConvert API 53

No x402, MPP or L402 (0). The credit cost of each conversion type is published (1, 2 or 4 credits, plus 1 a minute), and the API page says prices start at $0.008 a file at 10,000 files, but the price per credit is drawn by a script and was not read, per the 9 October check, so 15 of 20. Free plan of 10 credits a day with no card (20). A person signs up in a browser to create a key or approve OAuth (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

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

CloudConvert API 58

cloudconvert-cli 3.0.2 was published to npm on 21 October 2026 and adds an ai/agent command for the new AI tasks, which the privacy policy's dated entry of 19 October also records (30). In the 90 days from 3 August, the MCP server launch post (3 September), and Java 1.2.5, Ruby 1.2.0 (both 24 August) and CLI 3.0.2, the package tags counted half, so 2.5. The privacy policy's dated entry of 19 October records a policy text, not a release, and the ai/agent launch it describes is already counted through CLI 3.0.2 (0). No changelog. Support is a contact form and email, and dependency pull requests on the Java and CLI repositories were merged on 5 October and 23 October 2026. Issue replies were not read (8 of 15). Six official SDKs, four released in 2026. The Node.js SDK's last tag is still April 2025 (3.0.0) and the Python SDK's March 2022, and the MCP server is not in the official registry, searched on 1 November (12). Every SDK repository has a test workflow (8). 30 + 0 + 8 + 12 + 8 = 58.

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.

Security & auth CloudConvert API +15

CloudConvert API 71

API keys are created with any of six scopes and can be revoked, and OAuth 2.0 issues tokens for third-party clients, though the implicit grant is still supported and no key rotation is documented. Signed URLs carry an HMAC signature, not the key (27). A key limited to task.read is read-only, and the MCP server asks for three scopes, one of them task.write, plus the two webhook scopes for its webhook tools. No confirmation step for deletes (12). Results come back as download links, and the metadata and capture-website operations handle untrusted content. The MCP page tells users to connect only the official URL, with no prompt-injection guidance (6). The security page says all access is logged and reviewable by the customer in activity logs, and jobs can be filtered by API key (11). ISO 27001 from TÜV Süd, and a valid security.txt (re-read on 1 November, Expires 2027-05-01) with a disclosure policy and rewards only at CloudConvert's discretion, so no formal bounty. No public advisories and nothing on OSV for the SDK packages. That's above ahasend's 12 (ISO 27001 and a disclosure route, no security.txt) (15). 27 + 12 + 6 + 11 + 15 = 71.

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.

Schema & documentation PDFShift +10

CloudConvert API 59

No OpenAPI document was found in the docs or llms.txt. GET /v2/operations returns each operation's options with types, defaults and enum values, which is a machine-readable contract for options only. The MCP tool schemas sit behind OAuth and were not read (10 of 25). llms.txt, now listing 23 pages, and a Markdown twin of every docs page (10). The reference states what each endpoint does and when the synchronous variants are a poor choice, and the MCP tool list gives one line a tool, per the 9 October check (12). Task parameters are typed in the docs, but format options are found at run time through the operations endpoint and createJob takes an arbitrary task graph (10). Every operation has a raw request, CLI, cURL and SDK example, and the docs show 422, 429 and failed-task bodies with codes, with no full code list (11). The /v2 prefix and pinnable engine versions, with no changelog found (6). 10 + 10 + 12 + 10 + 11 + 6 = 59.

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.

Transparency & trust CloudConvert API +8

CloudConvert API 75

Closed service with terms (12 April 2022) that cover API use, and MIT SDKs (18). The privacy policy, now dated 19 October 2026, gives 24 hours for files, 72 hours for account data after deletion and 180 days for logs, which agrees with the docs' 24-hour task deletion. The 19 October update adds the AI chat and AI tasks, an AI log of requests, file names and results kept 180 days and used to fix errors and to evaluate and train the AI models for these functions, with an opt-out in the dashboard that deletes existing logs, which the AI docs repeat. A DPA is signed on request (25). No deprecation policy. The terms give 30 days' notice only if the whole service is discontinued, and the operations endpoint flags deprecated engine versions (5). Hosting, payment, support and AI companies are named with addresses (Claude through Amazon Bedrock in EU data centres, Qwen through OVHcloud), and regions are Germany and Virginia, with no separate sub-processor list (16). 18 + 25 + 5 + 16 = 64.

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.

Reliability CloudConvert API +7

CloudConvert API 80

Graded as a hosted service. Status page at status.cloudconvert.com (Better Stack) with nine components and 90-day bars (20). The incident list and RSS feed, re-read on 1 November, add one incident since 9 October, "iWork and Web are down" on 12 October. iWork recovered within two minutes and Web, the web interface rather than the API, recovered at 11:51 UTC on 13 October. With the EU Central slowdown on 8 October (from about 15:25 to 16:45 UTC), the US East, iWork and EU Central alert on 14 September and the other short incidents since 3 August, each touched one region, one conversion type or one component, so minor incidents only (20). Limits on creating jobs and tasks are described as dynamic, with X-RateLimit-Limit and X-RateLimit-Remaining headers and a free-plan cap of 5 concurrent tasks. The new ai/agent tasks have a fixed 6 requests a minute and 60 an hour, but the main endpoints have no fixed number per plan (8). A 429 carries Retry-After in seconds and the docs say CloudConvert retries retryable errors itself. No idempotency key (12). The terms promise 99.9 per cent monthly uptime with refunds on paid plans, re-read on 1 November (10). API v2 is generally available and the MCP server carries no beta label. Only the new ai/agent task is marked beta (10). 20 + 20 + 8 + 12 + 10 + 10 = 80.

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.

Score by category

CategoryWeightCloudConvert APIPDFShiftEdge
Reliability16%8073CloudConvert API +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5969PDFShift +10
Agent ergonomics13%6154CloudConvert API +7
Security & auth14%7156CloudConvert API +15
Payments & pricing10%5375PDFShift +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5877PDFShift +19
Transparency & trust7%7567CloudConvert API +8
Negative events≤1500
TotalB 66.2/100B 66.4/100

Facts side by side

FactCloudConvert APIPDFShift
KindHTTP APIHTTP API
VendorCloudConvert (Lunaweb GmbH)PDFShift
Hosted endpointhttps://api.cloudconvert.com/v2https://api.pdfshift.io/mcp
TransportsHTTPStreamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under CloudConvert's terms of service. The SDKs and the CLI on GitHub are MITnone
Tools exposed3411
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.cnicodeme/pdfshift
Last release2026-10-212026-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 noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity192 stars, 104k npm/wknone
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

CloudConvert API

API keys and OAuth tokens carry six scopes, the terms promise 99.9 per cent monthly uptime with refunds, and uploaded files are deleted within 24 hours. No OpenAPI document or changelog was found, the per-credit price is drawn by a script, and the MCP server now lists 34 tools with no subsets.

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

CloudConvert API

  1. Build each job from an import task, one or more processing tasks and an export/url task, then read the download links from the export task's result.files
  2. Call GET /v2/operations with include=options to find the options a format pair accepts before creating a convert task
  3. Do not retry a failed task automatically. CloudConvert retries retryable errors itself, and a retry endpoint creates a new task
  4. Download output within 24 hours. Tasks, files and export URLs are deleted after that
  5. Use https://sandbox.api.cloudconvert.com/v2 for tests. It consumes no credits and accepts only a fixed set of approved test files
  6. Turn off the AI log in the dashboard's AI settings before sending prompts or file names that shouldn't be kept for 180 days

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

PDFShift and CloudConvert API score within a point of each other on agent readiness, 66.4 (B) and 66.2 (B). CloudConvert API leads on reliability, agent ergonomics, security & auth and transparency & trust.

Do CloudConvert API and PDFShift need an API key?

CloudConvert API takes an API key or an OAuth sign-in. PDFShift needs an API key.

Can an agent call CloudConvert API and PDFShift without installing anything?

Yes. CloudConvert API has a hosted endpoint at https://api.cloudconvert.com/v2 and PDFShift at https://api.pdfshift.io/mcp.

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