If you have used Pressa to generate a document, you know the workflow: describe what you want, your AI agent generates LaTeX, Pressa compiles it, you get a perfect PDF. It works great for one-off documents. But what happens when you need the same type of document every month?
You end up re-describing the same layout, the same formatting, the same structure. Your agent generates slightly different LaTeX each time. The January invoice does not quite match the February invoice. The fonts are the same but the spacing is off, or the table columns shifted, or the header color is a shade darker. It is a small problem that compounds over time.
Saved Templates fix this. Create a document once, save the LaTeX source as a named template, and reuse it every time you need that document type. Same layout, same formatting, same structure - only the data changes.
The Problem With Starting From Scratch
Every time you ask an AI agent to create a document, it generates new LaTeX from your description. LLMs are probabilistic - they produce different output each run even with identical prompts. This is fine for creative writing. It is terrible for business documents that should look consistent.
Consider a monthly invoice workflow without templates:
Create a professional invoice for Acme Corp.
Invoice #INV-2026-001, dated January 15, 2026.
Line items: API usage $2,400, Support plan $499.
Use a clean layout with a navy header.The agent generates a great invoice. You send it. Next month:
Create a professional invoice for Acme Corp.
Invoice #INV-2026-002, dated February 15, 2026.
Line items: API usage $2,400, Support plan $499.
Use a clean layout with a navy header.Same prompt, different output. The table might use different column widths. The navy color might be #1B2A4A in January and #1A2B4B in February. The font size for the total might shift by half a point. Your client notices. It looks sloppy.
How Saved Templates Work
The workflow is straightforward. You create a document, perfect it through iteration, then save the LaTeX source as a named template. Next time you need that document type, you load the template, swap in new data, and compile. The layout is identical every time because you are using the exact same LaTeX source.
Step 1: Create and perfect your document. Use Pressa the normal way. Describe the document, iterate on the design, get it exactly right.
Step 2: Save it as a template. Once you are happy with the output, tell your agent to save it. The agent calls the save_template endpoint with a name and the LaTeX source.
Tool: pressa.save_template
Input: {
"name": "acme-monthly-invoice",
"latex": "\documentclass{article}\usepackage{geometry, booktabs...}..."
}
Result: {
"status": "success",
"name": "acme-monthly-invoice",
"message": "Template saved"
}Step 3: Reuse it. Next month, tell your agent to use the template with new data:
Use my "acme-monthly-invoice" template.
Change the invoice number to INV-2026-004,
the date to April 15, 2026,
and the amount to $5,000.The agent loads the template, modifies only the relevant values in the LaTeX source, and compiles. The result is pixel-identical to your January invoice except for the data that changed. Done in seconds.
Available Everywhere
Saved Templates work across all three interfaces. Whatever tool your AI agent or workflow uses, templates are available.
MCP Server. Four new tools: save_template, list_templates, get_template, and delete_template. Your AI agent in Claude Desktop, Cursor, or any MCP-compatible client can manage templates directly in conversation.
CLI. Four new commands under the templates namespace:
$ pressa templates list
acme-monthly-invoice (2.4 KB) Updated: Apr 13, 2026
quarterly-report (5.1 KB) Updated: Apr 10, 2026
nda-contract (3.8 KB) Updated: Apr 02, 2026
$ pressa templates get acme-monthly-invoice
# Outputs the LaTeX source
$ pressa templates save my-template --file template.tex
Template "my-template" saved.
$ pressa templates delete old-template
Template "old-template" deleted.REST API. Four endpoints for programmatic access: POST to create or update (upsert by name), GET to list all or fetch one, and DELETE to remove. Full details in the API documentation .
Templates Belong to You, Not Your API Key
One design decision worth noting: templates are tied to your user account, not to an individual API key. If you rotate your API key, regenerate credentials, or create a new key for a different environment, your templates are still there. This matters for teams that follow security best practices and rotate keys regularly.
Saving a template with the same name as an existing one overwrites it. This is intentional - it lets you iterate on templates without managing versions or dealing with name conflicts. Save the same name, get the updated version.
Plan Limits
The number of saved templates depends on your plan:
Free: 0 templates. Saved Templates are available starting on the Starter plan.
Starter: Up to 10 templates.
Pro: Up to 50 templates.
Business: Unlimited templates.
For most users, 10 templates cover the common document types - invoices, reports, contracts, letters, certificates. The Pro and Business tiers are for teams with diverse document needs or client-specific templates.
A Real Workflow Example
Here is a practical scenario. You run a consulting business and send invoices to three clients monthly. Without templates, that is three prompts describing three different invoice layouts each month. With templates:
1. Spend 10 minutes perfecting each client's invoice layout.
2. Save three templates: client-a-invoice, client-b-invoice, client-c-invoice.
3. Every month, tell your AI agent: "Use the client-a-invoice template, update the date to April 2026, hours to 42, rate to $150/hr." Three invoices, three sentences, done.
The time savings compound. Month one, you invest time creating templates. Month two onward, invoicing takes under a minute.
Get Started
Saved Templates are available now. If you are on the Starter plan or above, you can start saving templates immediately through the API, CLI, or MCP server.
Log in to your dashboard to check your plan, or read the documentation for detailed API reference and examples.