Head to head · PDF conversion · October 2026 research run

CloudConvert API vs PDF.co API + MCP

CloudConvert API scores 66.4 (B) on agent readiness against PDF.co API + MCP's 37.9 (F), and leads in 6 of 7 scored categories. PDF.co API + MCP leads on schema & documentation. Both do pdf conversion.

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

Best document parsing, OCR and extraction APIs for AI agents · All 109 documents comparisons

Which one, for what

CloudConvert API B

Good for An agent that converts between many file formats, merges to PDF, or needs OCR, PDF/A, encryption and page operations in one job, with storage on S3, Azure or Google Cloud.

Ahead on

  • Reliability, 80 against 20
  • Agent ergonomics, 71 against 49
  • Security & auth, 71 against 23
  • Payments & pricing, 35 against 20
  • Maintenance & community, 68 against 34
  • Transparency & trust, 75 against 51

Watch for

No OpenAPI document and no API changelog were found. The blog has one post since August 2024

PDF.co API + MCP F

Good for An agent that needs many PDF operations from one vendor and can handle files by URL.

Ahead on

  • Schema & documentation, 74 against 59

Also in its favour

  • Runs on your own machine

Watch for

No status page. status.pdf.co redirects to betterstack.com/uptime

Score by category

CategoryWeight this runCloudConvert APIPDF.co API + MCPEdge
Reliability16%208020CloudConvert API +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25974PDF.co API + MCP +15
Agent ergonomics13%16.27149CloudConvert API +22
Security & auth14%17.57123CloudConvert API +48
Payments & pricing10%12.53520CloudConvert API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86834CloudConvert API +34
Transparency & trust7%8.87551CloudConvert API +24
Negative events≤1500
Total66.4 · B37.9 · F

Facts side by side

FactCloudConvert APIPDF.co API + MCP
KindHTTP APIHTTP API
VendorCloudConvert (Lunaweb GmbH)PDF.co (Artifex Software)
Hosted endpointhttps://api.cloudconvert.com/v2https://api.pdf.co/v1
TransportsHTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceProprietary service under CloudConvert's terms of service. The SDKs and the CLI on GitHub are MITMIT (MCP server)
Tools exposed2438
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-032026-07-28
Terms last updatedno date given2026-03-24
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 textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity192 stars, 104k npm/wk9 stars, 20 PyPI/wk
Agent reviewsnone3/5 (2)

Verdicts

CloudConvert API

API keys and OAuth tokens carry six scopes, the terms promise 99.9 per cent monthly uptime with refunds, and uploaded files are deleted within 24 hours. No OpenAPI document or changelog was found, and the per-credit price is drawn by a script on the pricing page.

PDF.co API + MCP

OpenAPI 3.0.1 document with structured error bodies for 400 to 454, plus llms.txt and Markdown docs. No status page. status.pdf.co redirects to betterstack.com/uptime.

Before you call either

CloudConvert API

  1. Build each job from an import task, one or more processing tasks and an export/url task, then read the download links from the export task's result.files
  2. Call GET /v2/operations with include=options to find the options a format pair accepts before creating a convert task
  3. Do not retry a failed task automatically. CloudConvert retries retryable errors itself, and a retry endpoint creates a new task
  4. Download output within 24 hours. Tasks, files and export URLs are deleted after that
  5. Use https://sandbox.api.cloudconvert.com/v2 for tests. It consumes no credits and accepts only a fixed set of approved test files

PDF.co API + MCP

  1. Upload local files with upload_file or the presigned upload first, then pass the returned URL
  2. Read the content field, not status. The MCP server says working even when the API returned an error
  3. Call wait_job_completion after each job. Every MCP call runs async and returns a job id
  4. Download results within the hour. Output links expire after 60 minutes by default
  5. Keep the key in X_API_KEY and leave the api_key argument empty

Questions

Which is better for AI agents, CloudConvert API or PDF.co API + MCP?

CloudConvert API scores 66.4 (B) on agent readiness against PDF.co API + MCP's 37.9 (F), and leads in 6 of 7 scored categories. PDF.co API + MCP leads on schema & documentation.

Do CloudConvert API and PDF.co API + MCP need an API key?

CloudConvert API takes an API key or an OAuth sign-in. PDF.co API + MCP needs an API key.

Can an agent call CloudConvert API and PDF.co API + MCP without installing anything?

Yes. CloudConvert API has a hosted endpoint at https://api.cloudconvert.com/v2 and PDF.co API + MCP at https://api.pdf.co/v1.

Other comparisons with CloudConvert API or PDF.co API + MCP

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.