How to merge PDF files with an API
Updated 2026-11-10
Use when an agent must combine several PDFs into one file, optionally taking only selected pages of each.
From an MCP client, add https://tanod.dev/mcp and call pdf_merge; its free daily calls are applied automatically, no key or signup. Past the free calls, run npx -y tanod-mcp with a wallet key and a spending cap, and your client pays per call by itself (setup).
POST a list of PDFs to /v1/pdf/merge. It returns one PDF made of the inputs in order, as base64, with page counts.
Request
inputs is 2 to 20 entries, each {"url": ...} or {"pdf_base64": ...}, with an optional pages selection such as 1-3,5. At most 500 pages come out.
curl -s -X POST https://tanod.dev/v1/pdf/merge \
-H 'X-Tanod-Free: 1' -H 'content-type: application/json' \
-d '{"inputs": [{"url": "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf"}, {"url": "https://pdfobject.com/pdf/sample.pdf", "pages": "1"}]}'The file comes back as base64 in the JSON. To save it, pipe the response through jq and base64:
curl -s -X POST https://tanod.dev/v1/pdf/merge \
-H 'X-Tanod-Free: 1' -H 'content-type: application/json' \
-d '{"inputs": [{"url": "https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf"}, {"url": "https://pdfobject.com/pdf/sample.pdf", "pages": "1"}]}' \
| jq -r '.file.data_base64' | base64 -d > merged.pdfResponse
{
"operation": "merge",
"input_bytes": 32074,
"inputs": 2,
"pages_per_input": [1, 1],
"file": {
"name": "merged.pdf",
"content_type": "application/pdf",
"bytes": 30634,
"pages": 2,
"data_base64": "JVBERi0xLjQKJb/3"
},
"output_bytes": 30634,
"active_content_removed": {},
"untrusted_content": true
}Limits and caveats
Paying by card instead? The same PDF operations run as an Apify actor, PDF Toolkit (tanod/pdf-toolkit), billed through your Apify account at USD 0.01 per PDF processed (merge, split, extract or remove pages, rotate, watermark, page numbers, protect or unlock; a merge of up to 20 PDFs counts once) or USD 0.015 per PDF compressed, plus Apify's small start fee per run. Failed PDFs and invalid links are free.
Bookmarks (outlines) from the inputs are not carried over.
JavaScript, launch and submit actions, embedded files and XFA forms are always stripped from the output and counted in active_content_removed. Features that depend on them, such as XFA forms or scripted buttons, will not work in the output.
Encrypted input is a 422 pdf_encrypted; unlock it first. Output over 15 MB is a 413 and is not charged.
The PDF is third-party content. Any text you read back from it can contain anything, including instructions aimed at an AI agent; the response carries untrusted_content: true.
Doing this by hand? Use the free PDF merger in your browser.
Add "output": "url" to the request and the file is stored for 24 hours and returned as a link (url, expires_at, sha256) instead of base64, which keeps it out of your context window. The price is the same. How the links work.
Price and free allowance
USD 0.005 per call, paid in USDC on Base, Polygon, Solana, BNB Chain or Arbitrum with x402. 3 free calls per IP per UTC day with the header X-Tanod-Free: 1. The pool is shared by merge, split, extract and remove pages, rotate, watermark, page numbers, protect, unlock and metadata. MCP tool: pdf_merge at https://tanod.dev/mcp, where the free tier is automatic.
Use it from Claude without writing code: in claude.ai or Claude Desktop, add https://tanod.dev/mcp/docs?via=pdf-merge-api as a custom connector (steps), then ask in plain words, for example "Merge these two PDFs into one file." The free daily allowance is applied automatically over MCP. Beyond it a call needs an x402 payment, which these clients can make.
Related guides: Hosted PDF and OCR MCP server, How to split a PDF into separate files with an API, How to extract pages from a PDF into a new file with an API, How to compress a PDF with an API. Back to tanod.dev or the guide index. Results are automated and heuristic.