Docweave vs PDFEndpoint

Docweave is an MCP-native PDF/document-generation API: one REST call (or one MCP tool call) turns HTML, a URL, or a template + JSON into a PDF. The single biggest reason to consider it over PDFEndpoint is that combination — a first-class, open-source generate_pdf MCP tool paired with per-document pricing, rather than per-page or per-credit billing.

PDFEndpoint is an HTML- and template-to-PDF API that many teams already rely on for that core job — HTML or a template in, a real PDF out. Docweave covers the same ground and adds an MCP-native generate_pdf tool, per-document pricing, and template + JSON rendering. If you are building for AI agents or want to store a layout and bind data into it, that is where Docweave differs.

Where Docweave differs

 DocweavePDFEndpoint
MCP-native toolgenerate_pdf, open source (npx @docweave/mcp)See provider docs
Pricing modelPer documentSee provider pricing
SourcesHTML, URL, template + JSONHTML, template (see provider docs)
RenderingChromiumSee provider docs

Switching from PDFEndpoint

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 PDFEndpoint alternative?

For HTML- and template-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/template-to-PDF 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 an idempotencyKey so retried calls never double-generate the same document.

How does pricing compare?

Many HTML/template-to-PDF APIs bill per page, per conversion credit, or per plan tier. Docweave bills per document, so a long report and a one-page receipt are priced the same way. Check PDFEndpoint's current pricing page 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