Head to head · Pdf generate · October 2026 research run
DocRaptor vs PDFShift
PDFShift scores 66.4 (B) on agent readiness against DocRaptor's 55.6 (C), and leads in 5 of 7 scored categories. DocRaptor leads on agent ergonomics. Both do pdf generate.
Best PDF manipulation and conversion APIs for AI agents · All 67 pdf comparisons
Which one, for what
Best for Agents that already have HTML and CSS and need print-quality PDFs with Prince's paged-media support, or an XLSX from an HTML table.
Ahead on
- Agent ergonomics, 63 against 54
Watch for
One API key per account with no scopes, and the docs still offer it as the user_credentials query parameter
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 68
- Schema & documentation, 69 against 62
- Security & auth, 56 against 41
- Payments & pricing, 75 against 53
- Maintenance & community, 77 against 21
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.
Maintenance & community PDFShift +56
DocRaptor 21
Read as a closed service with open-source clients. The last dated product change found is the changelog entry of 5 September 2023, and the client libraries were last tagged in 2023 (docraptor-python 3.1.0 on 19 July 2023, npm docraptor 1.0.1 on 28 December 2023); the about and security pages were rewritten after the October 2025 acquisition but carry no dated API change (0). No releases in the last 90 days (0). Support by email, site chat and a help centre with stated hours, and a per-document help request from the dashboard; GitHub issue replies couldn't be read (8 of 15). Official clients in six languages exist and still match the API, but none has shipped since 2023 (10). The Python client pins 2023 dependencies and its test suite runs through tox with no CI workflow in the repository (3). 0 + 0 + 8 + 10 + 3 = 21.
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.
Payments & pricing PDFShift +22
DocRaptor 53
No x402, MPP or L402 (0). Plan prices are public and the plans page says overage is a per-document price by plan, with the per-document figures shown through a plan selector that our reader saw only for the Free plan (15). The Free plan has 5 documents a month and unlimited watermarked test documents, but the signup form shows card fields and no page says whether the Free plan needs a card (10). A person signs up in a browser (0). 0 + 15 + 10 + 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.
Security & auth PDFShift +15
DocRaptor 41
One API key per account with no scopes, sent as the HTTP Basic username, and the docs offer user_credentials in the query string as a second method, which costs the 10 points for a secret in a URL (0 of 30). Test mode limits spend but there is no read-only key, and the destructive action, expiring a hosted document, needs no confirmation (6). The API renders the caller's HTML and returns a PDF or spreadsheet, not text for the model to read (10). The dashboard's document log records each job with input, output and log when the account's retention allows, and an IP listing API exists; no per-key audit log (8). SOC 2 Type II, HIPAA BAAs, annual third-party penetration tests, a vulnerability disclosure policy with security@docraptor.com and DPF registration, but no security.txt (17). 0 + 6 + 10 + 8 + 17 = 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 DocRaptor +9
DocRaptor 63
Responses are the document bytes or a small JSON status, with X-DocRaptor-Num-Pages on PDFs, and test mode avoids spending quota (18). The document listing takes page and per_page (default 100); there is nothing else to page (12). XML error messages state the cause, the status-code page maps 400, 401, 403 and 422 to causes, and JavaScript errors are returned with the failure (14). No idempotency key and no safe-retry guidance; a retried POST makes a second document, and only test documents are free (4). Two parameters make a document, defaults are sensible, and official clients exist in Ruby, Python, Node, PHP, Java and C# (15). 18 + 12 + 14 + 4 + 15 = 63.
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.
Schema & documentation PDFShift +7
DocRaptor 62
An OpenAPI 3.0 description, docraptor.yaml with seven operations and a Doc schema, is public in the client repositories and generates the libraries, but it is not served from docraptor.com (18). No llms.txt and no Markdown twins (0). The API parameters page describes each option, when to use async, how pipelines map to Prince and JavaScript engines, and why both JavaScript engines shouldn't be enabled together (14). Options are listed with their allowed values and defaults, and the OpenAPI Doc schema types them, though nested prince_options are documented in prose (11). Examples in seven languages, a status-code page, an XML error example and the async failure body (11). Pipelines are versioned with a dated changelog, but its last entry is 5 September 2023 and the API path carries no version (8). 18 + 0 + 14 + 11 + 11 + 8 = 62.
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.
Reliability PDFShift +5
DocRaptor 68
Read with the hosted lines. status.docraptor.com is an Atlassian Statuspage with components (20). Its front page reported no incidents on any of the days it lists, the history page needs JavaScript our reader lacks, and history.rss redirects to an inactive feed, so the record is clean for the days we could read and unread beyond them (20). The limits page gives numbers, 60 seconds synchronous, 600 asynchronous, 30 simultaneous requests and 100 MB hosted output (15). Too many simultaneous requests answer 403 with no Retry-After or backoff guidance, callbacks are retried up to three times, and there is no idempotency key (3). No SLA found; the about page's 99.99 per cent uptime is a marketing figure and the terms are unread (0). GA (10). 20 + 20 + 15 + 3 + 0 + 10 = 68.
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
| Category | Weight | DocRaptor | PDFShift | Edge |
|---|---|---|---|---|
| Reliability | 16% | 68 | 73 | PDFShift +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 62 | 69 | PDFShift +7 |
| Agent ergonomics | 13% | 63 | 54 | DocRaptor +9 |
| Security & auth | 14% | 41 | 56 | PDFShift +15 |
| Payments & pricing | 10% | 53 | 75 | PDFShift +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 21 | 77 | PDFShift +56 |
| Transparency & trust | 7% | 69 | 67 | DocRaptor +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.6/100 | B 66.4/100 |
Facts side by side
| Fact | DocRaptor | PDFShift |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | DocRaptor, LLC (Artifex Software) | PDFShift |
| Hosted endpoint | https://api.docraptor.com/docs | https://api.pdfshift.io/mcp |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (client libraries) | none |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | io.github.cnicodeme/pdfshift |
| Last release | 2023-09-05 | 2026-11-05 |
| Terms last updated | 2026-06-03 | no date given |
| Privacy policy last updated | 2025-11-19 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 17k npm/wk | none |
How the scores have moved
PDFShift
No score change since it was listed.
Verdicts
DocRaptor
One POST turns HTML into a print-quality PDF or an Excel file, with published limits, free watermarked test documents and clients in seven languages. The single key can travel in a query string, there is no idempotency key, the terms page needs JavaScript our reader lacks, and nothing dated has changed since 2023.
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
DocRaptor
- Send the key as the HTTP Basic username with a blank password, never as
user_credentialsin the URL, and sendtest: truewhile iterating since test documents are free and watermarked - Use
async: truefor documents that may take more than 60 seconds, then poll/status/{status_id}untilcompletedand fetchdownload_urlwithin the account's retention period - Treat a 403 as either a permission problem or more than 30 simultaneous requests; back off and retry rather than fail the task
- JavaScript errors and, on pipelines before 7, console messages fail the document; set
javascript: trueonly when the HTML needs it and definedocraptorJavaScriptFinished()for async scripts - Do not retry a synchronous POST blindly after a timeout; check the document log or listing first, since each success counts against the monthly quota
PDFShift
- Send the key in the
X-API-Keyheader; a missing or malformed header falls back to the free tier silently, with watermarks and a 2 MB cap - Set
sandbox: truewhile testing; sandbox documents cost no credits and are limited to 10 a minute - Download the file from the returned URL within 2 days; the MCP
converttool andfilenameresponses keep files on S3 for that long only - Check the
X-Credits-Costheader andcredits_usagebefore large batches; a credit covers 5 MB, so a 14 MB PDF costs 3 - On 429, wait until the
X-RateLimit-Resettimestamp; authenticated keys get 250 conversions a minute
Questions
Which is better for AI agents, DocRaptor or PDFShift?
PDFShift scores 66.4 (B) on agent readiness against DocRaptor's 55.6 (C), and leads in 5 of 7 scored categories. DocRaptor leads on agent ergonomics.
Do DocRaptor and PDFShift need an API key?
Both need an API key.
Can an agent call DocRaptor and PDFShift without installing anything?
Yes. DocRaptor has a hosted endpoint at https://api.docraptor.com/docs and PDFShift at https://api.pdfshift.io/mcp.
Other comparisons with DocRaptor or PDFShift
- CloudConvert API vs DocRaptor
- CloudConvert API vs PDFShift
- ConvertAPI vs DocRaptor
- ConvertAPI vs PDFShift
- Foxit PDF Services API vs PDFShift
- iLoveAPI vs PDFShift
- Nutrient DWS Processor API vs PDFShift
- PDF.co API + MCP vs PDFShift
- pdfRest API Toolkit vs PDFShift
- DocRaptor vs Foxit PDF Services API
- DocRaptor vs iLoveAPI
- DocRaptor vs Nutrient DWS Processor API
- DocRaptor vs PDF.co API + MCP
- DocRaptor vs PDFMonkey
- DocRaptor vs pdfRest API Toolkit
- PDFMonkey vs PDFShift
Machine-readable
- This page as Markdown
/compare/docraptor-vs-pdfshift.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/docraptor.json·/api/v1/tools/pdfshift.json - From a terminal
anchor compare docraptor pdfshift(the CLI) - Over MCP
compare_tools {"a": "docraptor", "b": "pdfshift"}at/mcp, no key