pdfzen
Registry code: abd6e6a56a0cb0a8
pdfzen renders HTML to PDF for AI agents. Four tools:
list_starters — 45 public templates (free). Returns slug, name, description, dataKeys.
- endpoint
- https://api.pdfzen.site/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is pdfzen live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is pdfzen free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pdfzen have?
- 4 tools: render_html_to_pdf, render_template_to_pdf, get_starter, list_starters.
- Is pdfzen safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.4%· all time 99.4%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- list pdf templates
- get a template body
- render html to pdf
- render a template to pdf
- takes → gives
- data, code → documents
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-04
no flags
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_starters reads open 21h ago
List pdfzen's 45 public starter templates — invoices, receipts, contracts, certificates, NDAs, letters, reports, resumes, boarding passes, menus, bank statements, lab reports, lease agreements, performance reviews, and more. Returns an array of { slug, name, description, icon, pageOptions, fonts, dataKeys }. Free, no payment, no auth required. Call this first to discover what fits the user request, then optionally call get_starter to see the expected data shape, then call render_template_to_pdf to produce the PDF.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesrender_html_to_pdf reads unknown never probed
Prepare a paid PDF render from arbitrary Handlebars-flavoured HTML. Use only when no starter fits (one-off layouts, custom branding). Prefer render_template_to_pdf when a starter matches. Validates your HTML and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge.
{ "type": "object", "required": [ "html" ], "properties": { "css": { "type": "string", "description": "Optional CSS injected into the document head. Alternative to inline <style> in `html`." }, "data": { "type": "object", "description": "Handlebars context object resolved against the {{...}} expressions in `html`.", "additionalProperties": true }, "html": { "type": "string", "description": "The HTML body. Supports Handlebars {{ }} expressions resolved against `data`, plus pdfzen helpers ({{barChart}}, {{lineChart}}, {{pageBreak}}, {{#each}}, {{#if eq}}). Don't include <html>/<head>; just the body content + any <style> tags." }, "pageOptions": { "type": "object", "description": "Page format/margin/orientation. Defaults to A4 portrait. Example: { \"format\": \"A4\", \"margin\": { \"top\": \"20mm\" } }.", "additionalProperties": true } }, "additionalProperties": false }arguments 27 linesrender_template_to_pdf reads unknown never probed
Prepare a paid PDF render from one of the 45 starter templates. Validates your template + data and returns the exact, ready-to-execute HTTP request to run against pdfzen's render endpoint — POST /v402/render/pdf (x402, $0.006 USDC on Base, no API key) or POST /v1/render/pdf (pdfzen API key, credit-billed). pdfzen renders are executed over HTTP, not streamed in-band over MCP; this tool is the bridge. Your `data` is merged ON TOP of the starter sampleData at render time, so partial payloads inherit demo defaults (e.g. ship just the customer name + total).
{ "type": "object", "required": [ "template" ], "properties": { "data": { "type": "object", "description": "Handlebars context. Each starter expects a specific shape — call get_starter to see the sampleData and dataKeys for the chosen slug. Your fields merge ON TOP of sampleData, so you can supply only the fields the user gave you and the rest fall back to the demo content.", "additionalProperties": true }, "template": { "type": "string", "description": "Slug of the starter to render (e.g. \"invoice\", \"receipt\", \"certificate\"). Call list_starters first if unsure which fits the user request." }, "pageOptions": { "type": "object", "description": "Page format/margin/orientation overrides. Defaults come from the starter (most are A4 portrait). Example: { \"format\": \"Letter\", \"landscape\": true }.", "additionalProperties": true } }, "additionalProperties": false }arguments 23 linesget_starter reads unknown 21h ago
Fetch the full HTML body, CSS, sampleData, and pageOptions for one starter template by slug. Use this when you need to understand the exact shape of `data` the template expects before calling render_template_to_pdf, or when you want to fork a starter into custom HTML. Free, no payment, no auth required.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "The starter slug. Examples: \"invoice\", \"receipt\", \"certificate\", \"contract\", \"nda\", \"boarding-pass\", \"menu\". Call list_starters to discover all 45 slugs." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idabd6e6a56a0cb0a8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/abd6e6a56a0cb0a8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/abd6e6a56a0cb0a8?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.