HTML → PDF

An HTML to PDF API that agents can call without a canvas

ForgeDocs turns HTML into print-ready PDFs over HTTP or MCP. Pass a template pack, raw HTML, or Markdown — get a binary PDF (or PNG) back from the same Chromium pipeline.

Built for HTTP and coding agents

Most HTML to PDF APIs assume a Studio workflow. ForgeDocs is different: POST JSON to /api/v1/render, or let Cursor and Claude call MCP tools like render_template. Same schemas, same output — whether you are wiring a backend or an agent loop.

Templates when you want them, HTML when you don’t

Use opinionated packs for invoices, certificates, and packing slips, or send raw HTML for full layout control. Headers, footers, page size, and format (PDF or PNG) are request fields — not a separate product surface.

Async jobs when renders get heavy

For longer documents, queue work on /api/v1/jobs and optionally notify a webhook when the file is ready. Sync renders stay available for the playground and short payloads.

curl · HTML to PDF
curl -X POST https://pdfforagents.com/api/v1/render \
  -H "Content-Type: application/json" \
  -d '{
    "html": "<h1>Hello</h1><p>Printed by ForgeDocs.</p>",
    "format": "pdf"
  }' \
  --output hello.pdf

Common questions

What is an HTML to PDF API?+

It is an HTTP service that accepts HTML (or a structured template) and returns a PDF. ForgeDocs also accepts Markdown and template packs on the same endpoint.

Do I need a visual editor?+

No. ForgeDocs is agent- and API-first. Use packs for common docs, or pass HTML/Markdown when you already own the layout.

Can I try it before paying?+

Yes. Open the playground for free local trials, or start the Starter plan with a 7-day free trial ($8.99/mo after).

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.