The PDF
processing API.
The core PDF operations — generate, merge, split, compress, OCR, watermark, secure — as REST endpoints and MCP tools, behind one API key. The foundation the rest of the platform is built on.
Every PDF operation
you’ll reach for.
Generate from HTML, reshape, OCR, secure. One auth header, one base URL.
And there’s more — every endpoint, as both a REST call and an MCP tool, lives in the docs.
For most APIs, the file
is the finish line.
For us, it’s the starting line. One POST /docs and the PDF you just made enters the tracking platform.
A file.
Then nothing.
Generate it, reshape it, OCR it — then they hand you bytes and wave goodbye.
Just getting started.
Call it your way.
The same operation over plain REST, in your language, or as an MCP tool an agent calls itself.
curl -X POST https://apdf.io/api/pdf/file/create \ -H "Authorization: Bearer $APDF" \ -d '{ "html": "<h1>Invoice</h1>" }'
import requests requests.post( "https://apdf.io/api/pdf/file/create", headers={"Authorization": f"Bearer {APDF}"}, json={"html": "<h1>Invoice</h1>"}, )
# An agent calls the tool itself apdf.create-pdf-file({ "html": "<h1>Invoice</h1>" })