Docweave vs DocRaptor
DocRaptor is a long-running HTML/CSS-to-PDF service trusted for document-heavy workloads. Docweave handles the same core job and adds an MCP-native generate_pdf tool, per-document pricing, and template + JSON rendering alongside HTML and URL sources — all rendered with Chromium.
Where Docweave differs
- →MCP-native and agent-first. A first-class, open-source
generate_pdftool (npx @docweave/mcp) any MCP client can call — the legacy players do not ship this. - →Per-document pricing. You are billed per document rather than per page, so a long report and a short letter are priced the same way.
- →Three source types. Raw HTML, a public URL, or a stored/inline template with JSON data bound into it.
- →Chromium rendering. The same engine you develop against in the browser produces the final PDF.
Switching from DocRaptor
Send your HTML to a single endpoint and get a PDF back:
curl https://docweave.dev/api/v1/pdf \
-H "Authorization: Bearer dw_live_your_key" \
-H "Content-Type: application/json" \
-d '{
"source": { "type": "html", "html": "<h1>Quarterly report</h1>" },
"options": { "format": "Letter", "margin": "18mm" }
}' \
--output report.pdfFAQ
Is Docweave a DocRaptor alternative?
For turning HTML and CSS into a PDF, yes — you send a source and receive a PDF. Docweave also accepts a URL or a template + JSON, renders with Chromium, and ships a first-class MCP server so agents can call it directly.
What is different about Docweave's rendering?
Docweave renders with Chromium, so what you see in a modern browser is what you get in the PDF — the same CSS, fonts, and layout engine you already develop against.
How does pricing differ?
Many established PDF services bill per document or per credit tier. Docweave bills per document with transparent per-document pricing. Compare each provider's current pricing page for exact figures.
Can AI agents use Docweave directly?
Yes. The open-source Docweave MCP server (npx @docweave/mcp) exposes a generate_pdf tool to Claude, Cursor, and any MCP client, so an agent produces a PDF with a single tool call.
Try the MCP-native PDF API.
Get an API key