Why ASHDOCS exists.
ASHDOCS is a document and PDF API that turns the messiest part of business automation — files — into a single REST call. We built it because every workflow tool can move data, but almost none of them can convert, extract, redact or generate the documents that data lives in.
Who is ASHDOCS for?
Three groups, one problem. Developers who need PDFs generated, parsed or secured without operating a headless-browser fleet or a LaTeX toolchain. Automation builders in Make, Zapier, n8n and Airtable who hit the wall the moment a workflow touches a file — every endpoint is designed to drop into an HTTP module with no code. And ops and finance teams drowning in statements, invoices and contracts that need to become rows in a ledger, not attachments in an inbox.
What do we ship?
30 document tools behind one REST API and one X-API-Key header: HTML, URL, Markdown, Office and image conversion to PDF; merge, split, compress, rotate, watermark and page-level editing; AES-256 password protection and true text-removal redaction; OCR in 8 languages; and extraction — tables to CSV/XLSX, schema-driven PDF-to-JSON with per-field confidence, bank statements reconciled for Xero and QuickBooks, and PDF-to-Markdown for RAG pipelines. Around the tools: a no-code flow builder with 28 native app connections (Airtable, Stripe, Notion and more, with 5 more in active development), HMAC-signed webhooks, batch processing, and HTTP recipes for Make, Zapier and n8n.
How do we make money?
Credits. Every successful tool run costs a small, published number of credits — failed jobs are never charged, and sandbox keys (ash_test_) run every tool for free, forever. The free tier includes 100 credits a month with no card; paid plans start at $15/month. No per-seat pricing, no enterprise-only features, no sales call to see a price. The full grid is on the pricing page.
Who is behind ASHDOCS?
ASHDOCS is founder-built and independent. It started the way most tools worth using do: Ashwin Manikandan kept rebuilding the same document plumbing — render this, parse that, redact the other thing — inside every automation project, and decided the plumbing deserved to be a product. Today ASHDOCS runs as a lean product where the person who answers your support email is the person who wrote the endpoint. Questions, integration ideas or bug reports: ashwinmanikandan@ashdocs.com.