Munition
HTML to PDF

Your agent writes HTML.Your reader gets a PDF.

Turn a report, a brief or an invoice your agent wrote as HTML into an A4 PDF at a public link. Use the render_pdf tool from Claude, ChatGPT, Codex or Cursor, or call the HTTP route and pay each render with x402.

Quick start · HTTP + x402
Unpaid, this answers 402 with the price. Pay with any x402 client and send it again.
bash
curl -sS -i https://api.munition.io/v1/render/pdf \
  -H 'Content-Type: application/json' \
  --data '{"html":"<!doctype html><html><head><meta charset=\"utf-8\"><style>body{font-family:sans-serif;margin:40px}</style></head><body><h1>Weekly report</h1><p>Signups grew 12% this week.</p></body></html>","filename":"weekly-report"}'
Price
$0.02 per PDF
Input
Self-contained HTML, up to 1 MiB
Output
A4, up to 20 pages and 10 MiB
Link
Public, eligible for deletion after 7 days

Tools and routes

The same operation as an MCP tool, charged to a Munition account, and as HTTP routes paid per request. One fixed price each.

  • Render a PDF

    Send a complete HTML document, with its CSS inline and images as data: URIs, and get the PDF's public URL, size and page count.

    MCPrender_pdfconnector and local server
    $0.02
    x402POST /v1/render/pdf
    $0.02
    Example request body
    json
    {
      "html": "<!doctype html><html><head><meta charset=\"utf-8\"><style>body{font-family:sans-serif;margin:40px}</style></head><body><h1>Weekly report</h1><p>Signups grew 12% this week.</p></body></html>",
      "filename": "weekly-report"
    }

Use it in your AI app

Connect Munition once to Claude, ChatGPT, Codex or Cursor, then ask in plain words. The agent picks the tool.

  • “Write this week's results as a one-page HTML report, render it to PDF with Munition and give me the link.”

  • “Turn this table into an invoice and render it as a PDF with Munition.”

  • “Search the web with Munition for three sources on heat pumps, then render a two-page brief as a PDF.”

Two ways to pay

A Munition account

For the MCP tools. Connecting creates the account in one click, with no email and no API key. Each call is charged to its balance; when funds run out, the tool returns a top-up link (card where available, or USDC on Base). A connector connection spends at most $1 per call and $5 per 24 hours.

x402, per request

For the HTTP routes, with no account and no key. The route answers 402 with the price; the agent signs a USDC payment from its own wallet, on Base, Polygon, Arbitrum or Solana, and sends the request again.

How payment works

FAQ

No. The route takes the HTML itself, not a URL. Read the page first, then render your own HTML.

A self-contained document: CSS inline and images as data: URIs. Scripts, frames, forms and any outside request are refused, and the renderer runs offline with JavaScript off. The reference lists every rule.

No. A paid request is checked (JSON, schema, forbidden content) before its payment is verified, so a 400 costs nothing.

Reference

Every field, limit and error

Inputs, outputs, limits and what each route does when something fails after payment.