Docgent
Product How it works Developers Use cases Docs ↗
The document workspace for AI agents and humans

Google Docs for AI agents.

Give your agents one real document to work on — not another copy in another chat. They draft, research and revise. You see exactly what changed, edit anything, keep every version, and publish the document you actually approved.

One document. Any number of agents. Every change accounted for.

Agent request
Update the recommendation for the revised valuation range and carry the change through the executive summary.
Docgent revision
2 sections revised 1 key figure changed rest unchanged
Human
Review changes → edit → approve

AI made documents faster to write. It made them harder to manage.

An agent can produce a twenty-page report in minutes. Then the trouble starts. Ask for another pass and you get another copy. Correct a figure and it reappears two turns later. Edit the file yourself and the agent never sees your change. Hand it to a second agent and you've started another branch of reality. After enough iterations, nobody is sure which version is the version.

The document shouldn't live in the chat.

Chat draft
Report-v2.docx
Report-final.docx
Report-final-Andrew-edits.docx
New agent output
???
One Docgent document

Stop regenerating documents. Start working on them.

Chat is where work is instructed. Docgent is where the document lives. Every human and every agent works against the same canonical document — the one current state, not a fresh copy. Agents propose changes to that state. Humans review, edit and approve them. The approved state is where the next turn begins, for whoever or whatever takes it.

One canonical document

No competing attachments, chat outputs or "final-final-v3". There is always one current state.

Every change is explicit

See what an agent actually changed — sections, figures, recommendations, structure — without rereading the document.

Every decision survives

Human edits and approvals become part of the document's history. The next agent starts from what was accepted, not from what it last generated.

Track Changes for AI agents.

An agent can rewrite more in thirty seconds than you can comfortably review in thirty minutes. Docgent turns each pass into a revision you can actually review: the difference between the current document and the proposed one — which sections changed, which figures moved, what was left alone — instead of another twenty pages to reread.

Review the change, not the whole document again.

Agent changedr7 → current
Valuation range: $18–22m
+
Valuation range: $20–24m
Executive summary updated to match
Recommendation rewritten
Supporting evidence unchanged
Appendix unchanged
Accept
Edit
Comment
Send back
docs.docgent.io/inkl/publisher-cla
inkl/docgent-documents · inkl
Publisher Content Licence Agreement
AGREEMENT VERSION 2.0 DRAFT
Comparing r3 → currentSplit · Unified
40 sections added 23 prose edits 4 removed
documents/publisher-cla/doc.md
7.2 Inkl will notify Publisher before removing Content
+## 7.2 Inkl will notify Publisher before removing Content
7.3 New Publisher sign-off (editorial review)
+## 7.3 New Publisher sign-off (editorial review)
+## 7.4 Publisher will promptly notify Inkl of any material correction…
Approval
Current statusDraft
Revision history · 5
r5 3a44984CURRENT
Promote numbered sub-clauses to H2 headings
Docgent Agent (inkl) · 16 Aug
r4 60885f2
Add missing standard clauses: GST, force majeure, dispute resolution
Docgent Agent (inkl) · 15 Aug
r3 59c279c
Fix heading levels: primary clauses H1, sub-clauses H2
Docgent Agent (inkl) · 15 Aug
Full revision history alongside a live diff — every version has an identity, and every change has a reason.

One document. A continuous human–agent loop.

1 / Ask
Ask

Ask an agent to create, research or revise a document from wherever you already work.

2 / Agent works
Agent works

It reads the current document and works against that exact state — not a copy.

3 / Review
Review

Docgent shows the proposed revision and what changed. Edit directly, comment, accept, or send it back round the loop.

4 / Advance
Advance

The accepted revision becomes the document. The next person or agent starts from there.

The twentieth revision should be as understandable as the first.

docs.docgent.io
Docgent
Studio
Queue
Needs review2
In progress3
Done0
Documents
Needs review · 2
Shareholder Update FY26
Annual update — 3d ago
Review
Sponsored Posts: Performance Report
Strategic report — 4d ago
Review
In progress · 3
Publisher Content Licence Agreement
Agreement — 14m ago
Draft
Platform Modernisation
Memo — 1d ago
Draft
Weekly Funnel Report
Strategic report — 5d ago
Approved
Every document Docgent knows about, queued by what it needs from you next.

Documents have structure. Docgent keeps it — all the way to the page.

A real document isn't just paragraphs. It has key figures, recommendations, tables, evidence, citations, decisions and appendices — things with meaning.

key figures recommendations tables evidence citations decisions appendices
Docgent gives those elements stable structure that agents, validators and rendering systems all understand. The agent controls what the document says. Docgent controls what the document is. Your design system controls how it looks.

Because content and presentation are separate, the approved document renders straight to PDF, DOCX or web through your organisation's own typography, layouts and brand — consistently, every revision, with no manual reformatting.
Structured document
Brand system
PDF / DOCX / Web

The document you approve is the document that ships.

docs.docgent.io/inkl/publisher-cla/edit
5. Royalties and Payment
## 5.1 Track A — Per-Read Royalty
Where Track A is elected, Inkl will pay Publisher the Royalty Rate for each Premium Read in the relevant Quarter, subject to any Minimum Guarantee specified in Schedule 1.
## 5.2 Minimum Guarantee
Where a Minimum Guarantee is specified in Schedule 1, if the Premium Read royalty in any Quarter is less than the Minimum Guarantee, Inkl will pay the Minimum Guarantee for that Quarter.
05. Royalties and Payment

5.1 Track A — Per-Read Royalty

Where Track A is elected, Inkl will pay Publisher the Royalty Rate for each Premium Read in the relevant Quarter, subject to any Minimum Guarantee specified in Schedule 1.

5.2 Minimum Guarantee

Where a Minimum Guarantee is specified in Schedule 1, if the Premium Read royalty in any Quarter is less than the Minimum Guarantee, Inkl will pay the Minimum Guarantee for that Quarter.

Structured source on the left, the rendered document on the right — always in sync, always the same state.

Humans get a workspace. Agents get an interface.

Humans read, edit, comment and approve in a proper editor. Agents connect through the Docgent API or MCP to read the current state, pull relevant context and history, propose targeted or document-wide revisions, and respond to human feedback. Neither side has to impersonate the other — no agent clicking through a human editor, no human editing JSON.

Works with: Claude, ChatGPT, Cursor and custom agents via API.

REST API MCP OpenClaw
// agent reads the current document and proposes a revision const doc = await docgent.documents.get(docId); const revision = await docgent.revisions.propose(docId, { baseVersion: doc.version, changes: [{ section: "valuation", content: newValuationText }], }); await docgent.revisions.submit(revision.id);

For documents that go through real review.

Investment & transactions

Memoranda, valuations, due-diligence and deal materials that take dozens of substantive revisions before anyone signs.

Boards & executives

Board papers, committee packs and strategy documents where accuracy, provenance and sign-off matter.

Research & advisory

Deep research and recommendations produced quickly by agents, then shaped by accountable professionals.

Professional services

Client deliverables where the person whose name is on the document must stand behind every line.

Recurring reporting

Consistent reports across clients, entities or periods without giving up editorial control or design quality.

Open where it matters. Controlled where it counts.

Docgent is built on durable document primitives, not an opaque proprietary editing model. Your documents stay yours.

Portable source

Documents remain readable, structured source files you can take with you.

Complete history

Every revision has an identity. Every earlier state can be recovered.

Explicit approval

Nothing becomes canonical without a human decision.

Agent API

Agents work with documents programmatically instead of pretending to click through a human editor.

Give your agents somewhere proper to work.

They already know how to write. Give them a document they can come back to — one that remembers what humans changed, what agents changed, what was approved, and what happens next.

Agents do the writing. Humans stay in control.