Docweave vs Restpack

Docweave is an MCP-native PDF/document-generation API: one REST call turns HTML, a URL, or a template + JSON into a PDF, billed per document. Restpack offers HTML-to-PDF and screenshot APIs, but if you are building for AI agents, the biggest reason to consider Docweave is that it ships an open-source MCP server (generate_pdf) alongside per-document pricing, rather than a REST-only integration.

Where Docweave differs

 DocweaveRestpack
MCP-native toolgenerate_pdf, open source (npx @docweave/mcp)REST API
Pricing modelPer documentSee provider docs/pricing
SourcesHTML, URL, template + JSONHTML, URL (see provider docs for screenshot options)
RenderingChromiumSee provider docs/pricing

Switching from Restpack

The request shape is familiar — POST a source, get a PDF back:

curl https://docweave.dev/api/v1/pdf \
  -H "Authorization: Bearer dw_live_your_key" \
  -H "Content-Type: application/json" \
  -H "Accept: application/pdf" \
  -d '{
    "source": { "type": "html", "html": "<h1>Invoice #1024</h1>" },
    "options": { "format": "A4", "margin": "20mm" }
  }' \
  --output invoice.pdf

FAQ

Is Docweave a drop-in Restpack alternative?

For HTML-to-PDF, the shape is familiar: you POST a source and get a PDF back. Docweave accepts raw HTML, a URL, or a template + JSON, renders with Chromium, and returns the file. The main additions are a first-class MCP server and per-document pricing.

What does Docweave offer that a standard HTML-to-PDF and screenshot API does not?

An open-source, MCP-native generate_pdf tool (npx @docweave/mcp) that any MCP client — Claude, Cursor, and others — can call directly, plus template + JSON rendering so you can store a layout once and bind data into it.

How does pricing compare?

Many HTML-to-PDF and screenshot APIs bill per page, per conversion credit, or per API call tier. Docweave bills per document, so a long report and a one-page receipt are priced the same way. Check Restpack's current docs/pricing for exact numbers.

Can I use Docweave from an AI agent?

Yes. Add the Docweave MCP server and your agent gets a generate_pdf tool — one tool call instead of HTTP plumbing, with built-in idempotency so it never double-generates the same document.

Try the MCP-native PDF API.

Get an API key