# PDF.co API + MCP vs PDFShift (slim)

> PDFShift scores 66.4 (B) to PDF.co's 40.9 (E) for pdf conversion. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/pdf-co-vs-pdfshift.md (~4,500 tokens) · this version ~980 tokens · JSON https://www.anchorterminal.com/compare/pdf-co-vs-pdfshift.json · canonical https://www.anchorterminal.com/compare/pdf-co-vs-pdfshift
- 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-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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

- PDF.co API + MCP: E 40.9, rank #1370 of 1563 · https://www.anchorterminal.com/tools/pdf-co.min.md
- PDFShift: B 66.4, rank #490 of 1563 · https://www.anchorterminal.com/tools/pdfshift.min.md
- PDF.co API + MCP, good for An agent that needs many PDF operations from one vendor and can handle files by URL. Ahead on Schema & documentation, 74 against 69. Also Runs on your own machine.
- PDFShift, good 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 20; Security & auth, 56 against 23; Payments & pricing, 75 against 30; Maintenance & community, 77 against 64. Also Free to start without a card; No incidents deducted, where PDF.co API + MCP loses 3 points for them.

| Category | PDF.co API + MCP | PDFShift |
| --- | --- | --- |
| Reliability (16%) | 20 | 73 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 74 | 69 |
| Agent ergonomics (13%) | 53 | 54 |
| Security & auth (14%) | 23 | 56 |
| Payments & pricing (10%) | 30 | 75 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 64 | 77 |
| Transparency & trust (7%) | 67 | 67 |

| Fact (where they differ) | PDF.co API + MCP | PDFShift |
| --- | --- | --- |
| Vendor | PDF.co (Artifex Software) | PDFShift |
| Hosted endpoint | `https://api.pdf.co/v1` | `https://api.pdfshift.io/mcp` |
| Transports | HTTP, stdio | Streamable HTTP |
| Pricing | Paid | Freemium |
| Licence | MIT (MCP server) | none |
| Tools exposed | 38 | 11 |
| MCP registry | not listed | `io.github.cnicodeme/pdfshift` |
| Last release | 2026-10-22 | 2026-11-05 |
| Terms last updated | 2026-03-24 | no date given |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 9 stars | none |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, PDFShift +53: PDF.co API + MCP 20 (status.pdf.co still answers its robots.txt request with a 302 to incidents.betterstack.com marked `unpublished-status-page=true` (not followed), so there's no s…); PDFShift 73 (Read with the hosted lines.)
- Payments & pricing, PDFShift +45: PDF.co API + MCP 30 (No x402, MPP or L402 (0).); PDFShift 75 (No x402, MPP or L402 (0).)
- Security & auth, PDFShift +33: PDF.co API + MCP 23 (One API key per account in the `x-api-key` header, header only per the getting-started page and the OpenAPI document.); 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-…)
- Maintenance & community, PDFShift +13: PDF.co API + MCP 64 (On 3 November 2026 PDF.co retired its webpage screenshot endpoints, a dated API change per the changelog, and MCP 0.0.11 followed on 22 October (30).); PDFShift 77 (Read as a closed service with open-source clients.)
- Schema & documentation, PDF.co API + MCP +5: PDF.co API + MCP 74 (OpenAPI 3.0.1 at developer.pdf.co/openapi.json, linked from llms.txt under `OpenAPI Specs`, header-only `x-api-key` scheme (25).); 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).)
