Docweave vs Pdfcrowd

Docweave is an MCP-native HTML/URL/template-to-PDF API billed per document; the biggest reason to consider it over Pdfcrowd is that AI agents can call it directly as an MCP tool instead of integrating a per-language client library, with pricing that does not scale with page count. Pdfcrowd is an established HTML-to-PDF API with client libraries for many languages, and it covers the same core job — HTML in, a real PDF out. Where Docweave differs is an MCP-native generate_pdf tool, per-document pricing, and template + JSON rendering for storing a layout once and binding data into it.

Where Docweave differs

 DocweavePdfcrowd
MCP-native toolgenerate_pdf, open source (npx @docweave/mcp)REST API + per-language client libraries
Pricing modelPer documentSee provider docs/pricing
SourcesHTML, URL, template + JSONHTML, URL (see provider docs for full source types)
RenderingChromiumHTML-to-PDF engine (see provider docs)

Switching from Pdfcrowd

Instead of pulling in a Pdfcrowd client library for your language, POST a source directly and 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 Pdfcrowd 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 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 to Pdfcrowd?

Many legacy PDF APIs, including client-library-based ones like Pdfcrowd, bill per page or per conversion credit. Docweave bills per document, so a long report and a one-page receipt are priced the same way. Check Pdfcrowd's current pricing page for exact numbers.

Can I use Docweave from an AI agent instead of a client library?

Yes. Add the Docweave MCP server and your agent gets a generate_pdf tool — one tool call instead of installing and wiring up a per-language client library, with built-in idempotency so it never double-generates the same document.

Try the MCP-native PDF API.

Get an API key