Introduction
DocDealer turns typed templates into Word and PDF documents, over a REST API, an embedded editor, or MCP.
DocDealer turns typed templates into Word and PDF documents. A template is a schema: every field has a type and validation rules, and that one schema drives the UI form, the AI generation and the API. Anything the app can do, an HTTP call can do.
It is deliberately not a general-purpose agent. It makes one scoped AI call per document section, with the prompt assembled by the server — roughly 50× cheaper and 20× faster than an exploration loop over the same task. How generation works explains why.
Three ways in
REST API
You own the UI entirely. Create documents, push form values, generate, export.
Embedded editor
You own the surrounding app; DocDealer renders the collaborative editor in an iframe.
MCP
An AI agent drives DocDealer directly as a set of typed tools.
Authentication in one line
Every call carries an organization-scoped API key as a bearer token. The key already identifies the organization, so there is no tenant header to set.
curl https://thedocdealer.com/api/templates \
-H "Authorization: Bearer dd_live_xxxxxxxxxxxx"Keys are minted at /admin/api-keys and shown once. What a key may do is set by its
scopes and template allowlist.
Where to go next
Quickstart
From an API key to a generated .docx in a single request.
Concepts
Templates, rules, generation and versioning — the model behind the API.
Guides
Task-shaped walkthroughs: lifecycle, attachments, embedding, agents.
API reference
Every public endpoint, generated from the OpenAPI spec.
Machine-readable
The OpenAPI 3.1 document is public and needs no credentials, so you can point a generator at it:
curl https://thedocdealer.com/api/openapi.public.jsonIt is a curated view — admin-only and internal endpoints are left out. The MCP equivalent is at
/api/mcp/openapi.public.json. Every docs page is also available as raw markdown by appending .md
to its URL, and the whole corpus is at /llms-full.txt.