It grades its own pagination
autolayout re-renders until overflow, blank pages and orphan headings are gone, then returns a score out of 100 and every remaining issue with its page and its bounding box.
AI SmartTalk internal service · Rust · pandoc · WeasyPrint
A document engine
for our products
Markdown, HTML or Tera templates in. Paginated PDF, PNG preview, merge, watermark and AES-256 encryption out. One JSON API, one container.
The API serves AI SmartTalk teams and products: every call needs a token. Request access.
—version
—endpoints
—PDF engines
—status
What the service can do
— endpoints, one contract: binary PDF by default, a download URL when you ask for the file to be saved.
A document, its verdict, and its proof
Most engines hand you a file and leave you to discover the split table. This one grades what it produced, shows it, and can seal it.
It shows the pages
POST /api/preview returns the pages as PNG — one page, a range, or a contact sheet. An agent that writes markdown blind can finally see what it wrote.
It compares two versions
POST /api/diff answers with a pixel verdict, page by page. A renderer change that moves a single heading no longer passes for identical.
Thirty seconds to the first PDF
No SDK: HTTP and JSON, plus your token in the X-API-Key header.
Binary response by default
Without client_id/pdf_name, the response body is the PDF itself.
Server-side save
With both fields, the response becomes {"download_url": …} and the file stays served by the service.
Token required
Every /api/* needs X-API-Key. Only /api/health and /download stay open. Get a token.
md-to-pdf — fork maintained by
AI SmartTalk,
after the original project by
Spawnia.
Console
real requests from the browser
POST
/api/convert
idle
Internal service
Getting access
md-to-pdf runs for AI SmartTalk products and teams. It is not open self-service: every integration gets its own token.
1
Ask for a token
One mail with the project and the expected volume. Answer within one working day.
contact+mdtopdf@aismarttalk.tech
2
Store it here
The token stays in this browser and is used by every console request.
3
Test, then integrate
The console sends real requests with your token and hands you back the equivalent curl.
Where the token goes.
X-API-Key header or
Authorization: Bearer on every /api/*. Only
/api/health and /download/<client_id>/<pdf_name>
answer without authentication.
One token per integration. Do not commit it and do not put it in
front-end code: it grants full access to the engine. If it leaks, write to the same
address and we replace it.