AgentPay Doc Tools API vs BuildPDF API

Two free Documents & Productivity APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose AgentPay Doc Tools API if you want to start without an API key.
Choose BuildPDF API if its data fits your use case better; on access and reliability it's level with AgentPay Doc Tools API.

	AgentPay Doc Tools API	BuildPDF API
What it does	PDF to text, RSS/Atom/JSON feeds to JSON and sitemaps to URL lists, paid per call via x402.	Convert HTML, images, and text to PDF.
Provider	agentpay-tools.agentpay-apis.workers.dev	BuildPDF API
API key	Not needed	Required
HTTPS	Yes	Yes
CORS (browser calls)	Yes	Yes
Status today	Online · 657 ms	Online · 902 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

PDF to text, RSS/Atom/JSON feeds to JSON and sitemaps to URL lists, paid per call via x402.

PDF to text, RSS/Atom feeds to JSON, sitemaps to URL lists.

Strengths

Convert HTML, images, and text to PDF.

Convert HTML, images, and docs to PDF with a simple REST API. 100 free conversions/month. No sign-up friction.

Strengths

Prototyping or a tutorial? Pick the one that needs no API key.
Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
Still unsure? Both are free to try: send one request to each and compare the data you get back.

BuildPDF API requires an API key; AgentPay Doc Tools API doesn't, so AgentPay Doc Tools API is quicker to try.