ConvertAPI vs Foxit PDF Services API

ConvertAPI 92

OpenAPI 3.0.4 at v2.convertapi.com/info/openapi, 333 operations with token, JWT and secret schemes, plus per-conversion documents and wildcard listings (25). A long llms.txt written for agents (10). llms.txt tells agents to discover conversions rather than assume them and explains workflows and storage; converter pages describe each parameter (16 of 20). Per-converter parameter schemas in the OpenAPI document, validated by the MCP convert tool (12 of 15). 25 numbered error codes with meanings and examples throughout (14 of 15). v2 API and a dated public changelog (15). 25+10+16+12+14+15 = 92.

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.

ConvertAPI 80

Closed service. Newest changelog entry 5 November 2026 (30). Twelve dated entries from 1 October to 5 November (20). Public changelog, support email, phone and form, and SDK repositories on GitHub; issue replies not sampled (10 of 15). Current official SDKs, npm 1.16.0 on 26 October and PyPI 2.0.1 on 20 October 2026 (15). The MCP repository's last commit is 12 May 2026 and has no LICENSE file though its README says MIT; SDK CI not checked (5 of 10). 30+20+10+15+5 = 80.

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.

ConvertAPI 79

Four MCP tools that list, search and describe converters before one convert tool (25). StoreFile=true returns a URL and FileId instead of base64, and converters can be filtered by tag or search; nothing to paginate (14 of 20). Numbered codes such as 4014 balance exhausted and 5003 password protected an agent can act on (17 of 20). No idempotency key; a repeated conversion is billed again, and MCP tool annotations weren't found (8 of 20). SDKs in nine languages and a CLI, with one required file parameter on most converters (15). 25+14+17+8+15 = 79.

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.

ConvertAPI 55

Tokens per environment with usage limits, JWTs with expiry and IP restriction, a separate Master Token for admin endpoints, OAuth on the hosted MCP (30), less 10 for the documented Token query parameter and its Secret and Auth aliases (20 of 30). Usage limits per token, but no read-only token, and stored files can be deleted (8 of 20). Extracted text and OCR output come from the documents, with no prompt-injection guidance (3 of 15). Usage statistics and per-environment consumption through the Master Token (10 of 15). ISO 27001 certificate linked, SOC 2 Type 2 stated with the report on request, cyber insurance; no disclosure policy, security.txt or bug bounty found (14 of 20). 20+8+3+10+14 = 55.

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.

ConvertAPI 54

Hosted lines. status.convertapi.com is a Checkly dashboard drawn by script, so its components were not confirmed (10 of 20) and no history could be read (5). Concurrency per plan is published (1 to 4 concurrent conversions), with no request-rate figure (12 of 15). Under load the API answers 503 and llms.txt gives a 5, 10 and 15 second retry pattern; no 429, Retry-After or idempotency key (12 of 15). The compliance page states '99,95% monthly uptime' and says the SLA sits in the terms, but the terms read on 6 November state no uptime figure (5 of 10). Generally available (10). 10+5+12+12+5+10 = 54.

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.

ConvertAPI 25

No x402, MPP or L402 (0). Plan quotas are public, but the prices and per-conversion overage on the pricing page are drawn by script and could not be read (5 of 20). A free trial of 250 conversions with no card, per llms.txt (20). A person signs up in a browser (0). 0+5+20+0 = 25.

Foxit PDF Services API 40

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.