# DocRaptor vs Foxit PDF Services API

> 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.

- Canonical: https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services
- Markdown: https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services.md (~4,300 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

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: grade D, 53.3/100, rank #841 of 1349. Markdown https://www.anchorterminal.com/tools/docraptor.md · JSON https://www.anchorterminal.com/api/v1/tools/docraptor.json
- Foxit PDF Services API: grade D, 48.3/100, rank #1039 of 1349. Markdown https://www.anchorterminal.com/tools/foxit-pdf-services.md · JSON https://www.anchorterminal.com/api/v1/tools/foxit-pdf-services.json
- Best PDF manipulation and conversion APIs for AI agents: https://www.anchorterminal.com/best/pdf-tools/index.md
- All 43 pdf comparisons: https://www.anchorterminal.com/compare/pdf-tools/index.md

## Which one, for what

### DocRaptor (D)

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

Watch for: One API key per account with no scopes, and the docs still offer it as the `user_credentials` query parameter

### Foxit PDF Services API (D)

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 in its favour:
- Runs on your own machine

Watch for: OAuth client credentials carry no scopes, so every application credential can convert, delete and download


## 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).

## Score by category

| Category | Weight | DocRaptor | Foxit PDF Services API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 68 | 47 | DocRaptor +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 62 | 62 | even |
| Agent ergonomics | 13% (16.2 this run) | 63 | 49 | DocRaptor +14 |
| Security & auth | 14% (17.5 this run) | 41 | 40 | DocRaptor +1 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Foxit PDF Services API +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 21 | 38 | Foxit PDF Services API +17 |
| Transparency & trust | 7% (8.8 this run) | 69 | 63 | DocRaptor +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.3 · D** | **48.3 · D** | |

## Facts side by side

| Fact | DocRaptor | Foxit PDF Services API |
| --- | --- | --- |
| Kind | HTTP API | HTTP 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 |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| 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 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| 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 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 17k npm/wk | 12 stars, 47 npm/wk |

## How the scores have moved

### DocRaptor

No score change since it was listed.

### Foxit PDF Services API

- -0.1 on 28 October 2026: correction
- +0.1 on 27 October 2026: checklist

## 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.

**Foxit PDF Services API.** One credit per successful request, with failed calls, uploads, polling and downloads free, and a 500-credit yearly free plan. Access has no scopes, and the official MCP server reads and writes any local path. The status page has no component for the API, and no changelog was found.

## Before you call either

### DocRaptor

1. Send the key as the HTTP Basic username with a blank password, never as `user_credentials` in the URL, and send `test: true` while iterating since test documents are free and watermarked
2. Use `async: true` for documents that may take more than 60 seconds, then poll `/status/{status_id}` until `completed` and fetch `download_url` within the account's retention period
3. Treat a 403 as either a permission problem or more than 30 simultaneous requests; back off and retry rather than fail the task
4. JavaScript errors and, on pipelines before 7, console messages fail the document; set `javascript: true` only when the HTML needs it and define `docraptorJavaScriptFinished()` for async scripts
5. 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

### Foxit PDF Services API

1. Exchange the client ID and secret at `https://na1.fusion.foxit.com/oauth/token` and cache the Bearer token. `expires_in` is about 24 hours and there is no refresh token
2. Upload first with `POST /pdf-services/api/documents/upload`, start the operation, poll `GET /pdf-services/api/tasks/{task-id}` until `COMPLETED`, then download `resultDocumentId`
3. Read the body of a 429. It means either the rate limit (15 a minute in sandbox, 100 in production) or `QUOTA_EXCEEDED` when credits run out
4. Keep uploads under 100 MB, and delete documents with `DELETE /pdf-services/api/documents/{document-id}` when done. Deletion is permanent
5. With the MCP server, pass only paths the task needs. `upload_document` reads any `file://` path and `download_document` writes to any absolute path

## Questions

### Which is better for AI agents, DocRaptor or Foxit PDF Services API?

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.

### Do DocRaptor and Foxit PDF Services API need an API key?

DocRaptor needs an API key. Foxit PDF Services API uses an OAuth sign-in.

### Can an agent call DocRaptor and Foxit PDF Services API without installing anything?

Yes. DocRaptor has a hosted endpoint at https://api.docraptor.com/docs and Foxit PDF Services API at https://na1.fusion.foxit.com/pdf-services.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services.json, and with the fewest tokens: https://www.anchorterminal.com/compare/docraptor-vs-foxit-pdf-services.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "docraptor", "b": "foxit-pdf-services"}`. From a terminal: `anchor compare docraptor foxit-pdf-services`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/docraptor.json and https://www.anchorterminal.com/api/v1/tools/foxit-pdf-services.json

## Other comparisons with DocRaptor or Foxit PDF Services API

- [CloudConvert API vs DocRaptor](https://www.anchorterminal.com/compare/cloudconvert-vs-docraptor.md)
- [CloudConvert API vs Foxit PDF Services API](https://www.anchorterminal.com/compare/cloudconvert-vs-foxit-pdf-services.md)
- [Foxit PDF Services API vs iLoveAPI](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-iloveapi.md)
- [Foxit PDF Services API vs Nutrient DWS Processor API](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-nutrient-dws-processor.md)
- [Foxit PDF Services API vs PDF.co API + MCP](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-pdf-co.md)
- [Foxit PDF Services API vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-pdfrest.md)
- [DocRaptor vs iLoveAPI](https://www.anchorterminal.com/compare/docraptor-vs-iloveapi.md)
- [DocRaptor vs Nutrient DWS Processor API](https://www.anchorterminal.com/compare/docraptor-vs-nutrient-dws-processor.md)
- [DocRaptor vs PDF.co API + MCP](https://www.anchorterminal.com/compare/docraptor-vs-pdf-co.md)
- [DocRaptor vs PDFMonkey](https://www.anchorterminal.com/compare/docraptor-vs-pdfmonkey.md)
- [DocRaptor vs pdfRest API Toolkit](https://www.anchorterminal.com/compare/docraptor-vs-pdfrest.md)
- [Foxit PDF Services API vs PDFMonkey](https://www.anchorterminal.com/compare/foxit-pdf-services-vs-pdfmonkey.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp