# DocRaptor vs pdfRest API Toolkit (slim)

> pdfRest API Toolkit scores 57.7 (C) to DocRaptor's 53.3 (D) for pdf generate. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/docraptor-vs-pdfrest.md (~4,400 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/docraptor-vs-pdfrest.json · canonical https://www.anchorterminal.com/compare/docraptor-vs-pdfrest
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

pdfRest API Toolkit scores 57.7 (C) on agent readiness against DocRaptor's 53.3 (D), and leads in 3 of 7 scored categories. DocRaptor leads on reliability, agent ergonomics and transparency & trust. Both do pdf generate.

- DocRaptor: D 53.3, rank #841 of 1349 · https://www.anchorterminal.com/tools/docraptor.min.md
- pdfRest API Toolkit: C 57.7, rank #700 of 1349 · https://www.anchorterminal.com/tools/pdfrest.min.md
- DocRaptor, good 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 Reliability, 68 against 58; Agent ergonomics, 63 against 52; Transparency & trust, 69 against 62.
- pdfRest API Toolkit, good 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 62; Payments & pricing, 40 against 35; Maintenance & community, 70 against 21. Also Free to start without a card.

| Category | DocRaptor | pdfRest API Toolkit |
| --- | --- | --- |
| Reliability (16%) | 68 | 58 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 90 |
| Agent ergonomics (13%) | 63 | 52 |
| Security & auth (14%) | 41 | 37 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 21 | 70 |
| Transparency & trust (7%) | 69 | 62 |

| Fact (where they differ) | DocRaptor | pdfRest API Toolkit |
| --- | --- | --- |
| Vendor | DocRaptor, LLC (Artifex Software) | Datalogics, Inc. |
| Hosted endpoint | `https://api.docraptor.com/docs` | `https://api.pdfrest.com` |
| Licence | MIT (client libraries) | none |
| llms.txt | no | yes |
| Last release | 2023-09-05 | 2026-10-14 |
| Terms last updated | 2026-06-03 | no date given |
| Privacy policy last updated | 2025-11-19 | no date given |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 17k npm/wk | none |

Why the edge:
- Maintenance & community, pdfRest API Toolkit +49: 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.); 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.)
- Schema & documentation, pdfRest API Toolkit +28: 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.); 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.)
- Agent ergonomics, DocRaptor +11: 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.); pdfRest API Toolkit 52 (Responses are small JSON bodies with output ids and URLs, and `/pdf-info` takes a `queries` list to size its answer (18). Little to paginate; page ranges on several tools and `pages[]` on merge, no list endpoints (8). Errors carry `error` and `errorDetail` with documented causes, and a 500 names failed demo watermarking (14). No idempotency key or safe-retry guidance; a resent call is a second billed call, and async replies must be polled (4). Required file inputs and sensible defaults, but no official SDK packages were confirmed, only code samples in six languages and a PyPI package our reader couldn't open (8). 18 + 8 + 14 + 4 + 8 = 52.)
- Reliability, DocRaptor +10: 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.); 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.)
- Transparency & trust, DocRaptor +7: DocRaptor 69 (Closed service; the terms render through a script and were not read, the client libraries are MIT (12). The security FAQ states retention options, that logs hold metadata only, that content isn't used for model training and that metadata may be used for analytics, and the privacy policy on artifex.com of 19 November 2025 names the entities; the sub-processor list is a help-centre page that rendered empty for our reader (18). Pipelines 1 to 7 were deprecated with a dated notice in 2020 and pipeline versions are selectable, but there is no written notice period (12). AWS us-east-1 is named as the processing location and the FAQ says customers are emailed when the sub-processor list changes, though the list itself was unread (12). 12 + 18 + 12 + 12 = 54.); 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.)
- Payments & pricing, pdfRest API Toolkit +5: DocRaptor 35 (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.); pdfRest API Toolkit 40 (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.)