Introducing Autype V2: The Document Runtime AI Agents Were Missing

AI can produce pages of text in seconds. Producing a document that a company can actually reuse, review, automate, fill, sign, archive, and hand back to Microsoft Word is a much harder problem.

That is the problem Autype V2 was built to solve.

Over the last release cycle, we rebuilt Autype around a simple idea: a business document is not a blob of generated text and it is not just a downloadable file. It is a structured system of content, data, references, styles, pages, fields, revisions, and decisions.

Autype V2 turns that system into a workspace and a document runtime that humans, applications, and AI agents can use together.

More than an AI file generator

Most AI document workflows stop after creating a plausible-looking PDF or DOCX. That is useful for a first draft, but it breaks down when the document needs to survive real work.

A real report may include cross-references, figures, tables, citations, footnotes, a table of contents, reusable legal language, customer-specific data, different page designs, form fields, approvals, and an editable Word handoff.

Those parts are connected. Insert a figure and its number changes. Move a section and its references must follow. Update an approved clause and every linked document needs the right version. Add a form field and the final PDF must contain an actual interactive widget, not a rectangle that only looks like one.

Autype V2 models those relationships directly.

One document, several ways to work

V2 introduces a completely new visual Rich Text editor. It is the primary interface for people who want to create and edit full documents directly in Autype without working with markup or structured data. You can also switch to Autype Extended Markdown, inspect the complete JSON model, or let an AI agent make a targeted proposal.

Whichever surface you choose, you are working on the same document.

The rebuilt visual editor adds slash commands, drag-and-drop, contextual controls, advanced tables, images, charts, equations, QR codes, footnotes, citations, internal references, form fields, layouts, page sections, search, comments, and inline AI actions.

AI changes are reviewable. Autype can show a preview and diff before a proposed edit becomes part of the document. Proposals are tied to a revision so a delayed AI response cannot silently overwrite newer human work.

Extended Markdown built for documents

Markdown is an excellent interface for AI models, developers, and versioned content, but ordinary Markdown does not understand business-document page design or document semantics.

Autype Extended Markdown adds the missing document layer while keeping content readable. It can describe page sections, columns, fixed layouts, variables, reusable content, references, citations, footnotes, forms, charts, diagrams, indexes, and more.

That makes it useful as a common language between a human editor, an AI agent, the Developer API, and Autype's rendering system.

Native DOCX roundtrips

Word remains part of countless professional workflows. V2 therefore introduces a native OOXML import path for existing DOCX files.

Autype reads Word structures directly and reconstructs an editable document model. Supported headings, styles, lists, tables, images, sections, headers, footers, page settings, bookmarks, fields, references, captions, and footnotes remain available for editing and can be rendered back to DOCX.

There is no hidden Autype snapshot inside the Word file. If someone edits the document in Word, those Word structures are the source of truth when the file returns to Autype.

DOCX reconstruction is semantic rather than a byte-identical package clone. When a Word feature has to be normalized or cannot be represented safely, Autype reports structured diagnostics instead of silently pretending that nothing changed.

Real interactive PDF forms

Autype V2 can add text, number, multiline, date, checkbox, select, signature, and initials fields directly to the document model.

In a standard PDF export, those fields become real AcroForm widgets that recipients can complete. Fields can appear in normal document content and supported tables, and their visual style can be managed consistently with the rest of the document.

For archival or accessibility-oriented output, V2 also adds tagged PDF, PDF/A-1b, PDF/A-2b, PDF/A-3b, and PDF/UA-1 profiles. Interactive fields are flattened where required to protect the selected output profile.

Autype verifies the requested technical markers after rendering. As always, regulated use cases should perform their own final conformance and legal checks.

Page design without rebuilding every document

V2 introduces a complete reusable page-design system.

Styles can define Master, First, Odd, Even, Section First, and Blank pages. They can contain reusable headers and footers, page objects, backgrounds, bands, frames, shapes, images, fields, and different section layouts.

The new visual style editor provides a page canvas, direct manipulation, inspectors, layers, zoom, spreads, margin guides, undo and redo, and an authoritative rendered output preview.

Autype now includes 30 reusable system styles and 73 validated English document templates. Built-in styles can be attached directly without filling a workspace with copies. When a team wants to customize one, Autype creates an independent editable version.

Reuse recurring sections and data without losing control

Separate from the new editor itself, V2 adds resources that reduce repeated document work.

Reusable Blocks hold frequently used or approved sections such as disclaimers, service descriptions, policy language, and recurring report components. Teams can create a section once and reuse it across many documents instead of copying and maintaining it repeatedly. A document can reference the current block, pin a selected version, insert a snapshot, refresh it, or detach it for local editing.

Records hold typed customer, case, or project data for a document. Text, numbers, images, lists, and tables can be validated against the document's variables, previewed, saved, rendered again, and used in bulk generation.

Together, blocks and records separate what should remain consistent from what changes for each recipient.

A persistent document agent

The old one-shot assistant has been replaced with a persistent document agent.

The agent can work with the current document, selected workspace documents, attachments, styles, templates, reusable blocks, and research context. It can ask focused questions when essential information is missing, propose targeted changes, and preserve the proposal for later review.

Generation is Markdown-first, followed by deterministic validation and repair. The agent can also render pages as images for visual inspection before producing the final PDF or DOCX.

This is an important distinction: the model generates and reasons, while Autype remains responsible for document state, structure, validation, and output.

Review and approval on exact revisions

Autype V2 adds reusable document processes for work that cannot end at export.

The process builder and runtime now live directly inside Autype. Teams can design reusable process templates, start a process from the Workspace or the document editor, monitor running instances, and inspect completed history without moving the document into a separate review system.

Processes can combine document submission, review, QA checklists, sequential or parallel approval, manual tasks, PDF creation, attachment merging, watermarking, protection, compression, flattening, and signatures.

Each decision is attached to an immutable document revision. When changes are requested, a new revision enters the process without rewriting the history of earlier comments and decisions.

External participants can act through secure expiring links. Final process output and audit data remain connected to the exact source revision that was reviewed.

V2 supports typed-name simple electronic signatures and renders the signed result as a flattened PDF/A-2b document. It does not claim to provide a qualified or PAdES signature.

Built for APIs and AI agents

The Autype Developer API now exposes persistent Markdown documents, targeted document patches, reusable styles, blocks, records, templates, DOCX import, bulk rendering, PDF tools, visual page rendering, export-readiness checks, and multiple output formats.

The remote MCP integration now supports OAuth 2.1, explicit permissions, connected-app management, rotating refresh tokens, and a much larger document tool surface.

An agent can create a persistent document, inspect its outline, retrieve one relevant chunk, patch a bounded range with revision protection, validate the source, render page images, and finally export PDF, DOCX, or ODT without repeatedly sending the entire document through the model.

A new Workspace and Engine

V2 gives interactive and headless document work distinct surfaces inside the same product.

The Workspace focuses on documents, projects, libraries, templates, reusable resources, records, tools, and human processes. Search, filtering, sorting, pagination, full template previews, and recent documents make larger workspaces easier to navigate.

The Engine focuses on headless documents, resources, tools, runs, integrations, and usage. It can be activated with permanent pay-as-you-go automation credits without requiring a monthly editor subscription.

Use the full document toolkit from the Web app

V2 brings the complete PDF and conversion toolkit into Workspace → Tools. The same core operations available to developers can now be run manually in the browser without an API key.

Users can merge, split, rotate, reorder, watermark, inspect, protect, unlock, compress, fill, and flatten PDFs; convert PDF pages to images; convert DOCX, ODT, HTML, and images to PDF; replace typed DOCX placeholders; and run OCR, classification, filename generation, and structured extraction.

Uploads are temporary, job progress is visible, and completed results can be downloaded directly. Browser tool runs are included with an active Workspace editor plan rather than consuming Engine automation credits.

For automated work, Engine now has a dedicated Usage & credits area. It combines available and monthly credits, pay-as-you-go purchase history, and a searchable action log for API, MCP, render, and tool activity. Teams can inspect charged credits, execution status, duration, and reported model-token usage or export the history as CSV.

The foundation matters as much as the features

This release also includes a broad security and production-hardening effort: centralized authorization, scoped API keys, tenant isolation, private object storage, signed downloads, protected callbacks, safer remote file handling, secure OAuth flows, monitoring, release gates, safe migrations, and expanded end-to-end coverage.

These changes are less visible than a new editor button, but they are essential for production document workflows.

What Autype V2 changes

Autype V2 is built around a different definition of AI document generation.

The goal is not to produce a file that looks finished once. The goal is to create a document that remains structured, editable, reusable, reviewable, automatable, and reliable as it moves between people, systems, AI agents, PDF, and Word.

AI can write the text. Autype V2 builds and operates the document around it.

Explore Autype V2 or read the documentation.