# Stolid: HTML to PDF API for developers and AI agents

Stolid PDF renders HTML to PDF and returns stable warning codes for detected font, asset and layout issues, so your app or your AI agent can decide what to fix or review.

Free public preview: 500 live and 100 test calls a month, no card, keys by email. Try one template with [sample data](https://stolid.dev/data/): attach the CSS, images and fonts it needs, and keep each render within 20 pages, 30 seconds and a 6 MB request. [Request access](https://stolid.dev/access/) or write to hello@stolid.dev.

## HTML to PDF, with warnings your code can use

Send HTML to `POST https://api.stolid.dev/v1/pdf` with `Authorization: Bearer stolid_live_…`:

```bash
curl https://api.stolid.dev/v1/pdf \
  -H "Authorization: Bearer stolid_live_…" \
  -H "Content-Type: application/json" \
  -d '{"html": "<h1>Invoice 0042</h1> …"}'
```

A successful JSON response includes `status`, `pdf_url` and `manifest.warnings`. Each warning has a stable `code` and a `message`.

```json
{
  "id": "rnd_…",
  "status": "succeeded",
  "pdf_url": "https://…",
  "manifest": {
    "warnings": [
      {
        "code": "CONTENT_OVERFLOW",
        "message": "<table> extends 118px past the printable width and will be cut off."
      }
    ]
  }
}
```

## Render reports with stable warning codes

A PDF can render successfully and still use a substitute font or cut off a wide table. Every successful render includes a report that lists the issues Stolid detected, each with a stable code and a message. Use them to fix the template, log a warning or ask for a review.

| Code | What it means |
| --- | --- |
| `FONT_FALLBACK` | A font you asked for is not available; a similar one was used |
| `REQUEST_BLOCKED` | A file request was blocked. Send remote files in `assets` |
| `CONTENT_OVERFLOW` | Content extends past the page width or a clipping container |

The report lists the issues Stolid detects, such as missing fonts, blocked requests and overflowing content. An empty list means no warnings were reported; it does not guarantee that the layout is correct, so check the PDF as well. [See every warning code](https://stolid.dev/docs/warning-codes/).

## Give your agent useful feedback after every render

An agent can call the HTTP API today, read the warning codes and revise its HTML to fix the issues they describe. Your application sets the fixes, the retry limit and the final check. See [PDF generation for AI agents](https://stolid.dev/docs/ai-agents/).

1. Render: the agent sends its HTML and files to the Stolid PDF API.
2. Read codes: it reads the warning codes in `manifest.warnings`.
3. Fix: it edits the HTML or attaches the missing file.
4. Retry and check: it renders again, within a limit you choose. Then your workflow checks the PDF.

Available today:

- Readable by agents: `llms.txt`, a Markdown version of every page, and the OpenAPI description.
- Failed renders do not count: a render counts when it succeeds, including a render with warnings. Each revised document that renders successfully uses one call.
- Safe retries: repeat a request with the same `Idempotency-Key` within 24 hours and you get the original render, counted once. Use a new key when the document changes.
- A separate test allowance: 100 test calls a month in the preview, counted apart from your 500 live calls.

## Python and Node clients, or plain HTTP

Keep your HTML templates and send the files they need. Stolid runs the Chromium renderer; your application calls it over HTTP or through the typed Python and Node clients. The client package files come with your preview key email; publication on PyPI and npm is coming soon. If you run Puppeteer, wkhtmltopdf or WeasyPrint yourself today, Stolid PDF is a hosted option for the HTML-to-PDF part. See the [client guide](https://stolid.dev/docs/clients/).

```python
from stolid_client import StolidClient

client = StolidClient()  # reads STOLID_API_KEY
html = "<h1>Invoice 0042</h1>"
render = client.create_pdf(html)

for warning in render.warnings:
    print(warning.code, warning.message)
```

```js
import { StolidClient, getWarnings } from '@stolidhq/client';

const client = new StolidClient(); // reads STOLID_API_KEY
const html = '<h1>Invoice 0042</h1>';
const render = await client.createPdf(html);

for (const w of getWarnings(render)) console.warn(w.code, w.message);
```

## Pricing after the preview

The public preview is free: 500 live and 100 test calls a month, no card. The prices below are planned and may change before paid plans launch. See [Pricing](https://stolid.dev/pricing/).

| Plan | Price | Includes |
| --- | --- | --- |
| Free (planned) | $0, no card | Planned free tier: 100 calls a month |
| Pay as you go (planned) | Prepaid, from $5 | $0.01 per call |
| Build (planned) | $19 a month | 3,000 calls |
| Scale (planned) | $79 a month | 20,000 calls |
| Business (planned) | $249 a month | 100,000 calls |
| Enterprise (planned) | Custom | AWS Marketplace private offers |

1 call = one document, up to 20 pages and 30 seconds. Failed renders do not count. Renders with warnings count. Test calls are counted separately.

## Data handling

Know where your documents go.

- Documents sent to the API are rendered and stored on AWS in US East (N. Virginia), `us-east-1`.
- A render stays available through the API for 24 hours, and each download link works for one hour.
- During the public preview, use sample data. Keep real customer details, personal data and secrets out of requests.
- [Read the data handling page](https://stolid.dev/data/).

## Coming soon

On the way for agent builders. These are in development and are not available yet. Today, agents use the HTTP API.

- Hosted MCP server (coming soon): a remote MCP server with a Stolid PDF tool. It will use the same keys as the HTTP API.
- Optional page images (coming soon): images of the rendered pages, so an agent can look at the result next to the report.
- Spending caps per key (coming soon): a cap, in calls, on each key you hand to a script or an agent.
- Untrusted-content labels (coming soon): labels that help an agent tell document text apart from instructions.

## Try one template. Inspect the PDF and its report

Free public preview, access by request. Tell us what you would render and which language you use. We reply by email with the preview terms to accept, then your preview keys and the client package files. Bring one template and some sample data. [Request access](https://stolid.dev/access/) or write to hello@stolid.dev.

[Preview Terms](https://stolid.dev/legal/terms/) · [Acceptable use](https://stolid.dev/legal/terms/#acceptable-use) · [Privacy Policy](https://stolid.dev/legal/privacy/) · [Data handling](https://stolid.dev/data/) · Report abuse or copyright infringement: hello@stolid.dev

© 2026 Stolid · Operated by an individual in Washington, USA

Source: https://stolid.dev/
