HTML to PDF API

Renders a web page or an inline HTML string to a PDF, returned base64-encoded with its page count.

Updated

Agents read this page asGET /v1/html-to-pdf/schemafree: schema, examples, errors, price

Endpoint
POST /v1/html-to-pdf
Price
$0.005 per call
Timeout
12 s
max_timeout_seconds
33 (the whole call as the 402 envelope sells it: the timeout, plus payment verification and settlement around it)
Response cap
5 MB (5,242,880 bytes)
Family
Documents

When to use it

It needs a headless browser AND a hardened fetch: an agent that renders a URL itself walks the browser straight past every SSRF control, and carrying a Chromium is not something an agent does per call.

Your source is HTML and you need PDF.

When not to use it

  • The input is over 5 MB (5,242,880 bytes): html-to-pdf answers too_large (413).
  • The destination needs more than 12 s to answer: the call ends with upstream_timeout (424).
  • The destination is on a private or local network: the network guard refuses it with blocked_target (403).

Parameters

One JSON body. The schema is free at GET /v1/html-to-pdf/schema.

FieldTypeRequiredDescription
urlstringnoAbsolute http(s) URL of an HTML or XHTML page to fetch and render, up to 2048 characters; redirects are followed, the body is capped at 5 MB, and exactly one of url or html is required.
htmlstringnoSelf-contained HTML. Inline PNG data images are supported; external images, stylesheets and fonts are blocked. JavaScript is disabled.
formatstringnoPaper size of every page, A4 by default. One of: "A3", "A4", "A5", "Letter", "Legal", "Tabloid". Default: "A4".
landscapebooleannoPrint in landscape orientation instead of portrait. Default: false.

Limits

LimitValue
Largest source file5 MB (5,242,880 bytes)
Timeout12 s
Source formatsHTML
Output formatsPDF
Show the JSON Schema the handler validates against
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "url": {
      "description": "Absolute http(s) URL of an HTML or XHTML page to fetch and render, up to 2048 characters; redirects are followed, the body is capped at 5 MB, and exactly one of url or html is required.",
      "type": "string",
      "maxLength": 2048,
      "format": "uri"
    },
    "html": {
      "type": "string",
      "minLength": 1,
      "maxLength": 262144,
      "description": "Self-contained HTML. Inline PNG data images are supported; external images, stylesheets and fonts are blocked. JavaScript is disabled."
    },
    "format": {
      "default": "A4",
      "description": "Paper size of every page, A4 by default.",
      "type": "string",
      "enum": [
        "A3",
        "A4",
        "A5",
        "Letter",
        "Legal",
        "Tabloid"
      ]
    },
    "landscape": {
      "default": false,
      "description": "Print in landscape orientation instead of portrait.",
      "type": "boolean"
    }
  },
  "additionalProperties": false
}

Example

The published example, verbatim: the request and the response it returns.

Request
POST /v1/html-to-pdf
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "url": "https://grist.tools/samples/web/render-print.html",
  "format": "A4",
  "landscape": false
}

Without the payment-signature header the call answers 402 with the payment requirements, including this endpoint's price and its max_timeout_seconds, so the deadline is known before anything is paid. The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case we cannot state for you is a settlement call that fails without answering: the error message says so when that is what happened.

Response200 OK
200 OK
payment-response: <base64 settlement receipt>

{
  "source_url": "https://grist.tools/samples/web/render-print.html",
  "pages": 1,
  "bytes": 38404,
  "format": "A4",
  "landscape": false,
  "pdf_base64": "JVBERi0xLjcKJYGBgYEKCjYgMCBvYmoKPDwKL0ZpbHRlciAvRmxhdGVEZWNvZGUK...",
  "rendered_at": "2026-09-01T12:00:00.000Z"
}

Sample file: web/render-print.html. Printable one-page HTML table with inline CSS: a weekly rain gauge reading schedule.

In the sample itself, the document declares language en and the title "Rain Gauge Reading Schedule"; 1 style element carries 8 CSS rules; the body holds 28 td, 8 tr, 4 th, 1 a, 1 footer, 1 h1, 1 p, 1 table, 1 tbody and 1 thead elements; no script element; its heading reads "Rain Gauge Reading Schedule"; the table header cells are Day, Reader, Reading (mm) and Notes; its one link points to render-article.html. Across the whole file, the markup opens 53 tags, 3 of them inside the head. In the returned PDF: the file opens with the header line %PDF-1.7, then a comment of four bytes above 0x7F that marks the file as binary. The first object in the file is number 6, generation 0, a stream compressed with FlateDecode.

Response fields

FieldTypeIn the example
source_urlstring"https://grist.tools/samples/web/render-print.html"
pagesnumber1
bytesnumber38404
formatstring"A4"
landscapebooleanfalse
pdf_base64stringa string of 67 characters
rendered_atstring"2026-09-01T12:00:00.000Z"

Deterministic: the same input returns the same output. Clock-derived fields, when present, are declared in the response.

Call it from code

The client reads the 402, signs the payment and retries on its own.

// html-to-pdf: $0.005 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const body = {
  "url": "https://grist.tools/samples/web/render-print.html",
  "format": "A4",
  "landscape": false
}

const res = await fetchWithPayment('https://grist.tools/v1/html-to-pdf', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)

Errors

Every error is typed JSON. Only a successful call is settled.

CodeHTTPWhen
invalid_input400The body does not match the schema on this page. Nothing is charged. The body does not match the schema; its fields are url, html, format and landscape.
blocked_target403The destination is refused by the network guard: a disallowed address, or, for HTTP requests, a scheme other than http/https, a port other than 80/443, or credentials in the URL.
unreachable_target424The destination you named did not resolve or refused the connection.
upstream_timeout424The destination you named did not answer before the declared timeout for this endpoint expired.
too_large413The response exceeded the size cap while streaming, or decompressed at more than the allowed ratio.
unprocessable422The bytes arrived but could not be processed, for instance a malformed document.
internal500Our fault, and in almost every case nothing is charged. The exceptions come after the call has run and the settlement call was made: the message "The work was done but settlement could not be completed", and the messages starting with "Payment settlement returned". There, whether the payment moved is unknown to us as well. The payment moves at most once: its nonce is single-use and settlement is idempotent, so a retry with it is never charged twice. A retry is normally refused with a 402: replay_consumed, an expiry reason, or a reason saying the nonce was already used once the transfer is on-chain. Only if our server restarted before the transfer was final can a retry run the call again. Even then, the payment moves at most once. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain; to call again, sign a new payment.
rate_limited429Too many calls from the same payer, or too many calls towards the same destination domain. Nothing is charged.
concurrency_limit,
registry_at_capacity,
upstream_unavailable
503We could not serve the call right now. Retryable: wait the number of seconds in the retry-after header, then repeat the call. concurrency_limit and registry_at_capacity mean we were at capacity: the call did not run. You can send the same payment again if its validBefore is still far enough away to cover another call. If it is not, the retry gets a 402 authorization_validity_too_short: sign a new payment. upstream_unavailable means our internal service failed or did not answer in time: the call may already have run and the payment may have been settled. A retry with the same payment can get a 402 whose error field says why. authorization_validity_too_short: too little time is left before validBefore to cover another call. This check comes before the replay check, so it does not tell whether the first payment was settled. replay_consumed (the payment was used and may have been settled) or replay_exhausted (too many attempts): sign a new payment. replay_in_flight: the first call is still running, so wait and do not pay again. invalid_exact_evm_nonce_already_used: the transfer is already on-chain, so this payment cannot move again. Sign a new payment. An authorization can be settled only once, since its nonce is single-use. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain.
misconfigured503The service is not configured to serve calls. The call did not run and nothing is charged. It needs a fix on our side, so there is no retry delay to wait for.

Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.

Conversions

Ready-made calls to this API, one page each.

ConversionRecorded sampleSourceOutput
HTML to PDFweb/render-print.html1.4 KB37.5 KB

Questions

How much does a call to the HTML to PDF API cost?

$0.005 per call, paid in USD Coin on Base via x402. There is no account and no API key: the price is in the 402 answer, before anything is paid.

What is the timeout of html-to-pdf?

The endpoint itself runs for at most 12 s. max_timeout_seconds in the 402 answer is 33: that covers the whole call, including payment verification and settlement around it.

How large can a response from html-to-pdf be?

The response-size cap is 5 MB (5,242,880 bytes).

Is the html-to-pdf input schema free to read?

Yes. GET https://grist.tools/v1/html-to-pdf/schema returns the input schema for free, paid endpoints included.

What happens if a call to html-to-pdf fails?

The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case that cannot be stated in advance is a settlement call that fails without answering: the error message says so when that is what happened.

What does html-to-pdf return?

A JSON object with 7 top-level fields: source_url, pages, bytes, format, landscape, pdf_base64 and rendered_at. The example on this page is a real call over web/render-print.html.