Head to head · Pdf generate · October 2026 research run

PDFMonkey vs PDFShift

PDFShift scores 66.4 (B) on agent readiness against PDFMonkey's 61.8 (C), and leads in 4 of 7 scored categories. PDFMonkey leads on agent ergonomics and transparency & trust. Both do pdf generate.

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

Which one, for what

PDFMonkey C

Best for Agents that fill known templates with JSON to produce invoices, reports, forms and images, and teams that want an agent to author templates through the CLI.

Ahead on

  • Agent ergonomics, 75 against 54
  • Transparency & trust, 78 against 67

Also in its favour

  • Runs on your own machine

Watch for

One secret key with the whole account's privileges, no scopes and no read-only key

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 60
  • Schema & documentation, 69 against 61
  • Security & auth, 56 against 36
  • Payments & pricing, 75 against 60

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.

Agent ergonomics PDFMonkey +21

PDFMonkey 75

11 compact MCP tools from a 17 KB tools.ts, and API responses are cards without payload or logs on list and sync endpoints, while a full template fetch is large and the SDK docs warn about it (22). page[number], q[status], q[document_template_id], q[updated_since] and q[search] on document cards, q[folders] on templates and snippets, a meta block with pagination, and the CLI's --json (18). 401 and 422 bodies name the problem, 403 on an expired download URL is explained, and a quota overrun rejects the create rather than making a draft; the MCP server returns the API's error text (14). No idempotency key on create, so a retried create queues and bills a second document; webhooks are at least once with idempotency guidance; the MCP server sets no readOnlyHint or destructiveHint and delete_document is permanent, which the docs leave to the client to confirm (6). Only document_template_id and payload are needed, and official SDKs exist in two languages (Node.js and Ruby) plus the CLI (15). 22 + 18 + 14 + 6 + 15 = 75.

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.

Security & auth PDFShift +20

PDFMonkey 36

One secret key per account with the whole account's privileges, sent as a Bearer header; it can be rotated with a 2-day overlap and the old key revoked at once, but there are no scopes, no second key and no read-only key (12). No least-privilege mode; the MCP server exposes delete_document, the CLI asks before deletions unless -y, and the MCP docs say most clients ask before running a delete (6). The tools return the account's own templates, documents and quota, not third-party content (10). Each document carries generation logs and the dashboard shows usage, but no audit log or per-key activity view was found (3). No security.txt (404), no disclosure policy and no bug bounty; the compliance page says there is no SOC 2 or ISO 27001, and sets against that EU hosting, encrypted payloads and a DPA dated 15 October 2026 (5). 12 + 6 + 10 + 3 + 5 = 36.

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.

Payments & pricing PDFShift +15

PDFMonkey 60

No x402, MPP or L402 (0). Plan prices in euros, per-document pay-as-you-go rates and the Boost Pack price are on the public pricing page and in the docs (20). A Free plan of 20 documents a month and a 30-day Pro trial of 300 documents, no card (20). Signup is a browser flow and the key is minted in the dashboard (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.

Reliability PDFShift +13

PDFMonkey 60

Read with the hosted lines. status.pdfmonkey.io is an updown.io page with six checks (API, dashboard, preview, website, generation latency, queue size) and one month of rolling uptime per check, but no incident write-ups (15). The readable record is the uptime figures (API 99.98 per cent and queue 99.97 per cent since 3 October 2026) and the one incident the vendor wrote up, a slowdown of a little under an hour on 29 September 2026 with a post-mortem on 1 October; the 90-day list itself isn't published, so minor incidents only (20). The docs say there is no hard rate limit, only the monthly quota, so no request-rate numbers (5 for the quota numbers). The Node.js SDK retries 408, 429 and 5xx with backoff and honours Retry-After, and the webhook docs say delivery is at least once and to make handlers idempotent, but document creation has no idempotency key (10). No SLA found in the terms or pricing (0). GA (10). 15 + 20 + 5 + 10 + 0 + 10 = 60.

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.

Transparency & trust PDFMonkey +11

PDFMonkey 78

Closed service with iubenda terms that name the owner only as PDFMonkey at a Paris address, while the MCP server, CLI, Node SDK and Ruby gem are MIT (20). Retention statements agree across the plans page, the retention page and the data storage page (per-template TTL, 1 day, 7 days or unlimited by plan), the DPA and DsPA of 15 October 2026 are downloadable, and the privacy policy of 16 September 2026 names its processors, though it still lists Heroku where the docs name Fly.io (24). Engine deprecations were announced with a promised heads-up in 2023 and key rotation has a 2-day overlap, but there is no written deprecation policy with notice periods (8). Data locations are named (Paris and Frankfurt) and the DPA carries the approved sub-processor list (18). 20 + 24 + 8 + 18 = 70.

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.

Schema & documentation PDFShift +8

PDFMonkey 61

No OpenAPI document was found on pdfmonkey.io, in llms-full.txt or in the repositories; the 11 MCP tools carry JSON Schema inputs from src/tools.ts (12). llms.txt and llms-full.txt, and every docs page has a Markdown twin (10). MCP tool descriptions are one line each and say what the tool does, and the MCP docs say what the server can't do (create or edit templates) and send that job to the CLI; the API docs explain async against sync and when to use each (12). Parameter tables give types and required fields, list_documents has a status enum, and payload is by nature a free JSON object matched to the template (10). Request examples in curl, Ruby, Node.js, Python and PHP on every endpoint, a 401 body, a 422 body with field names and a troubleshooting section for blank documents, empty and 403 download URLs (12). The API lives under /api/v1 and docs pages carry a last-updated date, but there is no changelog page, changes are announced in blog posts such as What We Shipped Since the Summer of 26 October 2026 (5). 12 + 10 + 12 + 10 + 12 + 5 = 61.

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.

Score by category

CategoryWeightPDFMonkeyPDFShiftEdge
Reliability16%6073PDFShift +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6169PDFShift +8
Agent ergonomics13%7554PDFMonkey +21
Security & auth14%3656PDFShift +20
Payments & pricing10%6075PDFShift +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8177PDFMonkey +4
Transparency & trust7%7867PDFMonkey +11
Negative events≤1500
TotalC 61.8/100B 66.4/100

Facts side by side

FactPDFMonkeyPDFShift
KindHTTP APIHTTP API
VendorPDFMonkeyPDFShift
Hosted endpointhttps://api.pdfmonkey.io/api/v1https://api.pdfshift.io/mcp
TransportsstdioStreamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMIT (MCP server, CLI and SDKs)none
Tools exposed1111
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.pdfmonkey/pdfmonkey-mcpio.github.cnicodeme/pdfshift
Last release2026-10-262026-11-05
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity97 npm/wknone

How the scores have moved

PDFMonkey

PDFShift

No score change since it was listed.

Verdicts

PDFMonkey

An agent gets 11 compact MCP tools, a scriptable CLI and a sync endpoint, with public euro prices and a free plan. The one account-wide key has no scopes, document creation has no idempotency key, and there is no OpenAPI document, SLA or security disclosure policy.

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

PDFMonkey

  1. Use POST /api/v1/documents/sync or the MCP generate_document tool for one document; for batches create with status: pending and poll document_cards or take the webhook
  2. Fetch the template first (get_template or pdfmonkey template get --json) to learn the payload shape; a mismatched payload generates a blank or wrong document, not an error
  3. Download within the hour; download_url returns 403 after 60 minutes, and fetching the document again gives a fresh link
  4. Do not retry a create on a timeout without checking list_documents first; there is no idempotency key and each generation counts against the quota
  5. Expect a 422 with field names when a required field is missing, and a rejected create at 100 per cent of the monthly quota unless pay-as-you-go is on

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

PDFShift scores 66.4 (B) on agent readiness against PDFMonkey's 61.8 (C), and leads in 4 of 7 scored categories. PDFMonkey leads on agent ergonomics and transparency & trust.

Do PDFMonkey and PDFShift need an API key?

Both need an API key.

Can an agent call PDFMonkey and PDFShift without installing anything?

Yes. PDFMonkey has a hosted endpoint at https://api.pdfmonkey.io/api/v1 and PDFShift at https://api.pdfshift.io/mcp.

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