Head to head · PDF conversion · October 2026 research run

Foxit PDF Services API vs PDFShift

PDFShift scores 66.4 (B) on agent readiness against Foxit PDF Services API's 35.8 (F), and leads in every scored category. Both do pdf conversion.

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

Which one, for what

Foxit PDF Services API F

Best for An agent that needs conversion, page operations, protection, redaction, forms and OCR at a flat per-request price with free failures.

Also in its favour

  • Runs on your own machine

Watch for

Application credentials carry no scopes, and the MCP client sends the client ID and secret as headers on every call

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 30
  • Schema & documentation, 69 against 29
  • Agent ergonomics, 54 against 32
  • Security & auth, 56 against 30
  • Payments & pricing, 75 against 60
  • Maintenance & community, 77 against 18

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 +59

Foxit PDF Services API 18

The MCP server's last npm release read is 1.1.2 on 13 July 2026, 114 days before 4 November, so within 180 days (20 to 10, cause time). The public repository's last commit is still 23 January 2026 (re-read in a clone), npm could not be re-read without its JSON registry, and the developer blog feed is on a paused host. The API itself has no dated release notes. One release in the last 90 days as of 8 October and none since 6 August on what could be read (0). Per the 8 October check, two GitHub bug reports of 27 August 2026 and a fix submitted on 29 August were open, the newest developer forum topics had no replies, and support runs through a case form (6 of 25). The official MCP registry entry was read from the registry's data API, which is struck, and mcpName in package.json is a claim, not presence; no official API SDK was found (10 to 0). The repository has no CI workflow, no test files and no licence file, and its source stops at 0.2.3 while npm carries 1.1.2 (2 of 10). 10+0+6+0+2 = 18.

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.

Reliability PDFShift +43

Foxit PDF Services API 30

Foxit's General Terms of Service (27 June 2025) bar data mining or similar data gathering and extraction methods on Foxit's websites and web services, so foxit.com hosts were not requested beyond the two terms pages on 4 November and other foxit.com readings are per the 8 October check, not re-read. The OpenAPI YAML was found only in the reference page's script configuration, with no visible download link, so it and the credits, limits and authentication guides held in it are struck. 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; a vendor status page with no component for the product takes the settled 15 (8 to 15). With no component there is no readable incident history for this API (5). The rate limits (15 to 0) and the 429 backoff and credit-deduplication guidance (9 to 0) were read from the struck guides, and no other readable page states them. The trust centre states an aim of 99.99 per cent uptime, and the API Service Agreement, re-read on 4 November and still dated 30 June 2025, gives no availability warranty, so no SLA (0). PDF Services is generally available on the product page (10). 15+5+0+0+0+10 = 30.

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.

Schema & documentation PDFShift +40

Foxit PDF Services API 29

The OpenAPI YAML was found only in the reference page's script configuration, with no visible download link, so it and the credits, limits and authentication guides held in it are struck. The official MCP server's tools carry typed zod schemas in its public repository (0.2.3, 32 tools, re-read in a clone on 4 November) and in the npm 1.1.2 source read on 8 October (42 tools), with no linked contract for the API itself. Schemas in source code are not a published contract document, as a repository spec file with no visible download isn't (karrio, jambonz), so the contract line scores 0 (25 to 0). No llms.txt on either portal host and no Markdown twins, per the 8 October check (0). MCP descriptions state purpose and the upload, operate and poll order, but none says when not to use a tool (13 of 20, partial kept). Inputs are typed with optional fields marked, but the repository has three enums (rotation, page mode, scaling) and page ranges are free strings; the enums read from the YAML are struck (11 to 8). The README gives usage examples in prose, and tools return a code with a fallback such as CONVERSION_FAILED and a message, with no documented error table; the 235 YAML examples and coded bodies are struck (10 to 5). Package versions with no changelog; the YAML version number is struck (3 of 15). 0+0+13+8+5+3 = 29.

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.

Security & auth PDFShift +26

Foxit PDF Services API 30

The OpenAPI YAML was found only in the reference page's script configuration, with no visible download link, so it and the credits, limits and authentication guides held in it are struck. The MCP client source sends client_id and client_secret headers on every call, from an application created in the developer portal, with no scopes; token lifetime, rotation and the ban on query-string credentials came from the struck authentication guide, so revocation and rotation are not shown on readable evidence (20 to 10, one all-powerful credential). No read-only mode. Sandbox mode is the only separation. The MCP server has no annotations or confirmation step, delete_document is permanent, upload_document reads any file:// path, download_document writes to any absolute path, and the HTTP stream transport binds 0.0.0.0 (confirmed in http-server.ts on 4 November) with no authentication in the source (2 of 20). Extracted text, Markdown and HTML, and pages fetched by URL, are untrusted content with no injection guidance (0). Per the 8 October check, the dashboard shows credits used and remaining, and no per-call log is documented (4 of 15). Per the 8 October check, not re-read on 4 November, a disclosure policy with safe harbour, CVE numbering authority status, security bulletins and SOC 2 Type II for the cloud PDF APIs, with an expired security.txt and no bounty (14 of 20, partial kept). osv.dev lists no advisory for the npm package. 10+2+0+4+14 = 30.

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 PDFShift +22

Foxit PDF Services API 32

The OpenAPI YAML was found only in the reference page's script configuration, with no visible download link, so it and the credits, limits and authentication guides held in it are struck. 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 half of the earlier average rested on the struck YAML (10 to 5). Page ranges, extract types and image DPI limit output in the tool inputs, and nothing lists or pages stored documents (12 of 20). Tool errors carry a code and a message in the MCP source; the reading of the API's error bodies came from the struck YAML (14 to 8). The request_id deduplication came from the struck credits guide, and the MCP tools carry no readOnlyHint or destructiveHint in the source (6 to 0). Most tools need only a document ID. No official SDK package was found beyond the MCP server (7 of 15). 5+12+8+0+7 = 32.

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.

Payments & pricing PDFShift +15

Foxit PDF Services API 60

Foxit's General Terms of Service (27 June 2025) bar data mining or similar data gathering and extraction methods on Foxit's websites and web services, so foxit.com hosts were not requested beyond the two terms pages on 4 November and other foxit.com readings are per the 8 October check, not re-read. No x402, MPP or L402 (0). The pricing page publishes the price per unit without a login, 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). Total 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.

Score by category

CategoryWeightFoxit PDF Services APIPDFShiftEdge
Reliability16%3073PDFShift +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%2969PDFShift +40
Agent ergonomics13%3254PDFShift +22
Security & auth14%3056PDFShift +26
Payments & pricing10%6075PDFShift +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1877PDFShift +59
Transparency & trust7%6367PDFShift +4
Negative events≤1500
TotalF 35.8/100B 66.4/100

Facts side by side

FactFoxit PDF Services APIPDFShift
KindHTTP APIHTTP API
VendorFoxit Software IncorporatedPDFShift
Hosted endpointhttps://na1.fusion.foxit.com/pdf-serviceshttps://api.pdfshift.io/mcp
TransportsHTTP, stdioStreamable HTTP
AuthOAuthAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the Foxit API Service Agreement. The MCP server is MIT per its package.json, with no licence file in the repositorynone
Tools exposed4211
Read-only variant documentednono
llms.txtnoyes
MCP registryio.github.foxitsoftware/foxit-pdf-api-mcp-serverio.github.cnicodeme/pdfshift
Last release2026-07-132026-11-05
Terms last updated2025-06-30no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity12 stars, 47 npm/wknone

How the scores have moved

Verdicts

Foxit PDF Services API

The pricing page lists $1,750 a year for 5,000 credits and a 500-credit yearly free plan, and the official MCP server's tools carry typed schemas. Credentials carry no scopes, the MCP server reads and writes any local path, the status page has no component for the API, and no changelog or linked API contract was found.

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

Foxit PDF Services API

  1. Set FOXIT_CLOUD_API_HOST, FOXIT_CLOUD_API_CLIENT_ID and FOXIT_CLOUD_API_CLIENT_SECRET for the MCP server. The client sends the ID and secret as headers
  2. Upload first, start the operation, poll the task until its status is COMPLETED or FAILED, then download resultDocumentId, as the MCP tools do
  3. Delete documents with DELETE /api/documents/{document-id} when done. Deletion is permanent
  4. With the MCP server, pass only paths the task needs. upload_document reads any file:// path and download_document writes to any absolute path
  5. Run the MCP server over stdio, or put its HTTP mode behind a firewall. It binds 0.0.0.0 with no authentication

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, Foxit PDF Services API or PDFShift?

PDFShift scores 66.4 (B) on agent readiness against Foxit PDF Services API's 35.8 (F), and leads in every scored category.

Do Foxit PDF Services API and PDFShift need an API key?

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

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

Yes. Foxit PDF Services API has a hosted endpoint at https://na1.fusion.foxit.com/pdf-services and PDFShift at https://api.pdfshift.io/mcp.

Other comparisons with Foxit PDF Services API 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.