Markdown → PDF
Markdown to PDF API for docs, reports, and agent output
Agents and backends already speak Markdown. ForgeDocs accepts a markdown field on the render endpoint, styles it for print, and returns a PDF — no separate converter or canvas required.
One endpoint for Markdown, HTML, and packs
Pass markdown for long-form content, html for full control, or a template id for invoices and certificates. You do not need a second product surface to move between formats.
Fits agent-written content
When an agent drafts a report or changelog in Markdown, pipe it straight to ForgeDocs. MCP clients can call the same render path used by your HTTP workers.
Combine with merge when needed
Generate several Markdown PDFs, then POST /api/v1/merge (or MCP merge_pdfs) to combine them into a single deliverable for customers or compliance packs.
curl -X POST https://pdfforagents.com/api/v1/render \
-H "Content-Type: application/json" \
-d '{
"markdown": "# Weekly report\n\n- Shipped invoice pack\n- Fixed merge edge case\n",
"format": "pdf"
}' \
--output report.pdfCommon questions
How is Markdown to PDF different from HTML to PDF?+
Markdown is converted to styled HTML first, then printed with the same Chromium pipeline. Use Markdown for prose; use HTML when you need pixel-level layout.
Can I include images and tables?+
Standard Markdown constructs are supported through the HTML conversion step. For complex layouts, prefer HTML or a template pack.
What is the pricing?+
Free soft quota to try locally. Starter is $8.99/mo after a 7-day free trial.
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.