# DocRaptor vs Foxit PDF Services API (slim)

> DocRaptor scores 53.3 (D) to Foxit PDF Services's 48.3 (D) for pdf generate. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services.md (~4,300 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services.json · canonical https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services
- 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)

DocRaptor scores 53.3 (D) on agent readiness against Foxit PDF Services API's 48.3 (D), and leads in 4 of 7 scored categories. Foxit PDF Services API leads on payments & pricing and maintenance & community. Both do pdf generate.

- DocRaptor: D 53.3, rank #842 of 1349 · https://www.anchorterminal.com/tools/docraptor.min.md
- Foxit PDF Services API: D 48.3, rank #1038 of 1349 · https://www.anchorterminal.com/tools/foxit-pdf-services.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 47; Agent ergonomics, 63 against 49; Transparency & trust, 69 against 63.
- Foxit PDF Services API, good for An agent that needs conversion, page operations, protection, redaction, forms and OCR at a flat per-request price with free failures. Ahead on Payments & pricing, 40 against 35; Maintenance & community, 38 against 21. Also Runs on your own machine.

| Category | DocRaptor | Foxit PDF Services API |
| --- | --- | --- |
| Reliability (16%) | 68 | 47 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 62 |
| Agent ergonomics (13%) | 63 | 49 |
| Security & auth (14%) | 41 | 40 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 21 | 38 |
| Transparency & trust (7%) | 69 | 63 |

| Fact (where they differ) | DocRaptor | Foxit PDF Services API |
| --- | --- | --- |
| Vendor | DocRaptor, LLC (Artifex Software) | Foxit Software Incorporated |
| Hosted endpoint | `https://api.docraptor.com/docs` | `https://na1.fusion.foxit.com/pdf-services` |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | OAuth |
| Licence | MIT (client libraries) | Proprietary service under the Foxit API Service Agreement. The MCP server is MIT per its package.json, with no licence file in the repository |
| Tools exposed | none | 42 |
| MCP registry | not listed | `io.github.foxitsoftware/foxit-pdf-api-mcp-server` |
| Last release | 2023-09-05 | 2026-07-13 |
| Terms last updated | 2026-06-03 | 2025-06-30 |
| Privacy policy last updated | 2025-11-19 | no date given |
| Terms restrict automated access | yes | not found in the text |
| Popularity | 17k npm/wk | 12 stars, 47 npm/wk |

Why the edge:
- Reliability, DocRaptor +21: 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.); Foxit PDF Services API 47 (Read with the hosted lines. status.foxit.com keeps 90-day component history for Foxit's cloud products, but has no component for the API gateway at na1.fusion.foxit.com or for PDF Services (8 of 20). With no component there is no readable incident history for this API (5). Rate limits are published as 15 requests a minute in sandbox mode and 100 in production mode, per application, over a rolling 60 seconds (15). The limits guide asks for exponential backoff on 429 and the credits guide says a retried request is not charged twice, but no Retry-After header is documented and 429 also signals an exhausted credit quota (9 of 15). The trust centre states an aim of 99.99 per cent uptime, and the API Service Agreement gives no availability warranty, so no SLA (0). PDF Services is generally available, with structural extraction marked trial (10).)
- Maintenance & community, Foxit PDF Services API +17: 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.); Foxit PDF Services API 38 (The MCP server's last npm release is 1.1.2 on 13 July 2026, 87 days before this check. The API itself has no dated release notes (20 of 30). One release in the last 90 days and no dated changelog entries (0). On GitHub, two bug reports of 27 August 2026 and a fix submitted on 29 August are still open, and the newest topics on the developer forum have no replies. Support runs through a case form (6 of 25). The server is in the official MCP registry under io.github.foxitsoftware, but the entry lists 0.2.3 from December 2025 (10 of 15). The repository has no CI workflow, no tests and no licence file, and its source stops at 0.2.3 while npm carries 1.1.2 (2 of 10).)
- Agent ergonomics, DocRaptor +14: 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.); Foxit PDF Services API 49 (The MCP server at 1.1.2 has 42 tools in about 89 KB of source with no toolsets, the more-than-30 band (5). The API returns a document ID, not the file, and takes page ranges, so responses stay small (15). We averaged the two to 10 because the listing covers both. Page ranges, extract types and image DPI limit output, and nothing lists or pages stored documents (12 of 20). Errors are JSON with a code and a message that names the valid values, and a failed task reports its error (14 of 20). Credits are deduplicated by a `request_id`, but no header for a client to set one is documented, and the MCP tools carry no `readOnlyHint` or `destructiveHint` (6 of 20). Most operations need only `documentId`. No official SDK package was found beyond the MCP server (7 of 15).)
- Transparency & trust, DocRaptor +6: 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.); Foxit PDF Services API 63 (A closed service under a dated API Service Agreement (30 June 2025). The MCP server is MIT per package.json with no licence file (17 of 30). The agreement says uploaded documents are deleted within 30 days. The privacy policy says uploads are deleted when processing completes and outputs typically within a day, and it states an effective date of 10 May 2022. It says customer documents are not used to train AI models. No DPA was found (14 of 30). The agreement promises prior notice of changes with no period, and there is no deprecation policy (4 of 20). Server locations are named as the United States, Germany, Canada, Australia and Japan, the API host is a single na1 address, and no sub-processor list for the API was found (9 of 20).)
- Payments & pricing, Foxit PDF Services API +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.); Foxit PDF Services API 40 (No x402, MPP or L402 (0). The price per unit is public without a login. One credit per successful request, at $1,750 a year for 5,000 credits or $4,500 for 15,000 (20). The Developer plan gives 500 credits a year and the sign-up page asks only for an email address. We did not go past that page, so a later card step is unchecked (20). A person signs up in a browser to get the client ID and secret (0).)