Foliant

Templates that always come out the same

Every card is a real render of the template below it, made by the same engine that serves the API. Copy a template into your account, send your data as inputs, get the PDF. Agents get a fixed layout they cannot drift from; you get documents that look like they came from one hand.

Bundled fonts only (Libertinus Serif, Noto Sans, New Computer Modern, DejaVu Sans Mono), no packages, no external files unless you pass a logo. Each template also compiles with no inputs at all, so partial data never breaks a render.

Rendered Invoice template, first page Invoice1 page · A4 · 15 inputs Rendered Quote template, first page Quote1 page · A4 · 13 inputs Rendered Contract for signature template, first page Contract for signature1 page · A4 · 8 inputs Rendered Letter template, first page Letter1 page · A4 · 13 inputs Rendered Report template, first page Report1 page · A4 · 8 inputs Rendered Meeting minutes template, first page Meeting minutes1 page · A4 · 8 inputs Rendered Delivery note template, first page Delivery note1 page · A4 · 10 inputs Rendered Manual template, first page Manual3 pages · A4 · 7 inputs Rendered CV template, first page CV1 page · A4 · 10 inputs Rendered Certificate template, first page Certificate1 page · A4 landscape · 7 inputs

How to use one

  1. Open a template and press Copy to my account (sign in first, it is free). It lands under /templates/<name>.typ in your account.
  2. Render it by name: POST /v1/render with { "template": "invoice.typ", "inputs": { ... } }, or ask your agent through MCP: "render the invoice template for Northwind, total 8 496.60".
  3. Edit the Typst in the dashboard when the layout should change. Every render after that uses the new version.

Lists (line items, clauses, steps) travel as JSON strings inside inputs and are parsed with json(bytes(...)). Pass a logo as an attached file or a stored asset and set inputs.logo to its path. The templates guide explains the patterns.