Skip to content
External endpointresponds

pdfzen

Render PDFs from 45 starter templates or raw HTML. Pay-per-render with USDC via x402.

Endpoint URL
https://api.pdfzen.site/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
346 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
site.pdfzen/render

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
pdfzen
Version
1.0.0
Capability keys
tools
Tool names
list_starters, get_starter, render_template_to_pdf, render_html_to_pdf
Instructions excerpt

pdfzen renders HTML to PDF for AI agents. Four tools: list_starters — 45 public templates (free). Returns slug, name, description, dataKeys. get_starter — full template body + sampleData for one slug (free). render_template_to_pdf — prepare a paid render of a starter (returns the ready HTTP request). render_html_to_pdf — prepare a paid render of custom HTML (returns the ready HTTP request). Typical flow: list_starters → pick → get_starter (inspect dataKeys) → render_template_to_pdf. IMPORTANT: pdfzen renders are executed over HTTP, not streamed in-band over MCP. The two render tools validate your request and hand back the exact call to POST to the render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key; use an x402 client like x402-fetch or Coinbase Agent Kit) or POST /v1/render/pdf (pdfzen API key, credit-billed). Execute that HTTP call to get the PDF bytes back (200 application/pdf). Docs: https://pdfzen.site/

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 268ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 342ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 215ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 346ms