Docweave vs Nutrient (formerly PSPDFKit)

Docweave is an MCP-native document-generation API: one REST call turns HTML, a URL, or a template + JSON into a PDF, billed per document. The biggest reason to consider it over Nutrient (formerly PSPDFKit) is scope — if you just need to generate PDFs (especially from an AI agent), Docweave is a lighter, MCP-first alternative to a full document SDK.

Nutrient, formerly known as PSPDFKit, is a document SDK and PDF processing platform used for viewing, editing, annotating, and converting documents across web, mobile, and server. It is a broader toolkit than Docweave; Docweave narrows in on one job — generating a PDF from a source — and adds an MCP-native generate_pdf tool and per-document pricing on top of a plain REST API.

Where Docweave differs

 DocweaveNutrient (formerly PSPDFKit)
MCP-native toolgenerate_pdf, open source (npx @docweave/mcp)See provider docs/pricing
Pricing modelPer documentSee provider docs/pricing
SourcesHTML, URL, template + JSONSee provider docs/pricing
RenderingChromiumSee provider docs/pricing

Switching from Nutrient (formerly PSPDFKit)

If all you need is document generation, replacing an SDK integration with a single API call can be this simple — 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 Nutrient (formerly PSPDFKit) alternative?

Not exactly — Nutrient is a broad document SDK and processing platform (viewing, editing, annotating, converting, and more), while Docweave is a focused document-generation API. If the job is turning HTML, a URL, or a template + JSON into a PDF, Docweave covers it with one REST call. For in-browser document viewing/editing SDK features, check Nutrient's current docs.

What does Docweave offer that a general document SDK does not?

An open-source, MCP-native generate_pdf tool (npx @docweave/mcp) that any MCP client can call directly, plus simple per-document pricing and a single POST /api/v1/pdf endpoint with no SDK to install or license.

How does pricing compare?

Nutrient's pricing depends on the product line and deployment model — see the provider's current docs/pricing for specifics. Docweave bills per document generated, so a one-page receipt and a long report cost the same to render.

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 or SDK integration, with an idempotencyKey so retries never double-generate the same document.

Try the MCP-native PDF API.

Get an API key