Blog
Playbooks for turning what your AI agent writes — proposals, reports, runbooks — into consistent, print-ready documents.
One API call returns every recoverable table in a PDF as rows and CSV, tagged with page provenance. Deterministic first — a table that can't be recovered honestly comes back as a warning, never a half-guessed grid.
Read postGovernment filings, insurance claims, onboarding packets — the answers are already structured data. Two API calls put them on the official form: inspect the fields for free, then fill them. No Acrobat, no browser bot, no silent drops.
Read postInkrun now extracts structured, grounded data from PDFs — invoices, receipts, contracts — through the same MCP server and API that render your agent's PDFs. One key, one credit meter, both directions.
Read postLLMs are excellent at content and unreliable at design. Giving an agent raw HTML/CSS control creates drift and a security hole. The fix is an old idea: separate content from form.
Read postPandoc, VS Code extensions, md-to-pdf, Puppeteer, HTML-to-PDF APIs, and hosted services — what each is actually good at, and how to pick for your case.
Read postConnect the Inkrun MCP server to Claude Desktop or claude.ai and turn any conversation into a designed, print-ready PDF — no copy-pasting into Google Docs.
Read post