A simple API for rendering HTML and CSS into reliable, pixel-perfect PDFs. Built for developers.
REST API · Browser rendering · MCP included
<div class="invoice">
<h1>Invoice #1042</h1>
<p>Acme Inc.</p>
<table>
<tr>
<td>Website development</td>
<td>$899</td>
</tr>
<tr>
<td>Hosting</td>
<td>$350</td>
</tr>
</table>
<strong>$1,249.00</strong>
</div>Invoice #1042
Acme Inc.
| Website development | $899 |
| Hosting | $350 |
API
No PDF libraries. No layout engine to maintain. Just HTML, CSS and an API request.
curl https://api.tupsara.com/v1/pdf \
-H "Authorization: Bearer pdf_live_..." \
-H "Content-Type: application/json" \
-d '{
"html": "<h1>Invoice #1042</h1>",
"format": "A4"
}'{
"id": "a3f1c2e4-...",
"status": "completed",
"download_url": "https://.../a3f1c2e4-....pdf?X-Amz-...",
"file_size_bytes": 18420,
"render_duration_ms": 812
}Why Tupsara
You already know how to build documents with HTML and CSS. Tupsara lets you use the same technologies to generate PDFs.
Traditional PDF generation
Tupsara
Capabilities
Generate PDFs with a single HTTP request — send HTML, get back a finished document.
$ curl api.tupsara.com/v1/pdf -d '{ html }'
Use the web technologies you already know.
Render documents using a real browser engine for reliable web layouts.
Give AI agents the ability to generate production-ready documents.
Rendering engine
Tupsara uses browser-based rendering so your PDFs can use the same layout techniques you already use on the web.
Chromium is the initial rendering engine. Tupsara is designed to support multiple rendering engines over time.
Use cases
Generate branded invoices automatically.
Turn application data and dashboards into printable reports.
Generate dynamic documents from structured application data.
Create branded certificates and documents at scale.
MCP
MCP included · No additional costGive AI agents the ability to create real, production-ready documents.
Works with Claude Code, Claude Desktop, and the claude.ai connector. See the connection guide →
Developer experience
Pick the interface that fits your stack — the underlying rendering call is identical.
POST /v1/pdf HTTP/1.1
Host: api.tupsara.com
Authorization: Bearer pdf_live_...
Content-Type: application/json
{
"html": "<h1>Invoice #1042</h1>",
"format": "A4"
}curl https://api.tupsara.com/v1/pdf \
-H "Authorization: Bearer pdf_live_..." \
-H "Content-Type: application/json" \
-d '{
"html": "<h1>Invoice #1042</h1>",
"format": "A4"
}'// conceptual example — no official SDK yet
const res = await fetch("https://api.tupsara.com/v1/pdf", {
method: "POST",
headers: {
Authorization: "Bearer pdf_live_...",
"Content-Type": "application/json",
},
body: JSON.stringify({
html: "<h1>Invoice #1042</h1>",
format: "A4",
}),
});
const pdf = await res.json();// tool: generate_pdf — one of 8 tools on Tupsara's MCP server
{
"tool": "generate_pdf",
"arguments": {
"html": "<h1>Invoice #1042</h1>",
"format": "A4"
}
}Architecture
Why "Tupsara"
Thousands of years ago, scribes recorded contracts, transactions and knowledge on clay tablets.
In ancient Mesopotamia, scribes were known as ṭupšarru.
Tupsara takes inspiration from that idea: a modern infrastructure layer for creating reliable documents.
FAQ
HTML + CSS into PDF.
The initial renderer is Chromium-based.
No. Tupsara is API-first and can be used with standard HTTP requests.
Yes. Any document that can be represented with HTML and CSS can be generated.
Yes. MCP support is included at no additional cost.
Support custom fonts where supported by the rendering environment.
Give it a reliable way to become a PDF.