PDF tools

Merge PDF API for combining invoices, packs, and agent output

POST an ordered list of PDF sources — base64, HTTPS URLs, or project paths — and ForgeDocs returns one concatenated file. Same auth and quotas as render; MCP merge_pdfs for coding agents.

Start 7-day free trial Try the playground Starter $8.99/mo →

One call after you generate the pieces

Render invoices, quotes, certificates, or Markdown reports with /api/v1/render, then merge them for customers, auditors, or email attachments. Order is preserved from your sources array.

Flexible source shapes

Each item can be a raw base64 string, an https URL, a path under the ForgeDocs tmp tree, or an object with base64 | url | path. Cap is 30 PDFs per merge — enough for typical compliance packs.

REST and MCP together

HTTP clients hit POST /api/v1/merge. Agents call merge_pdfs and get back an absolute path (and optional base64) for the merged file — no canvas, no desktop Acrobat step.

curl · merge PDFs

curl -X POST https://pdfforagents.com/api/v1/merge \
  -H "Content-Type: application/json" \
  -d '{
    "sources": [
      { "url": "https://example.com/invoice.pdf" },
      { "url": "https://example.com/packing-slip.pdf" }
    ]
  }' \
  --output merged.pdf

Common questions

How does the merge PDF API work?+

Send a non-empty sources (or pdfs) array. ForgeDocs normalizes each source, concatenates pages in order, and returns application/pdf.

Can I merge files I just rendered with ForgeDocs?+

Yes. Generate PDFs via /api/v1/render or MCP, then pass their URLs, paths, or base64 into merge — a common quote → invoice → packing-slip bundle.

What does Starter cost?+

Starter is $8.99/mo after a 7-day free trial. Merge usage shares the same monthly quota model as renders.

Ready to generate documents from your stack?

Starter is $8.99/mo after a 7-day free trial. Use the playground locally, or wire MCP / REST when you're ready to ship.

Start 7-day free trial Open playground