Documint for AI agents
Documint is a document generation platform that creates dynamic PDFs and other files from reusable templates, used by teams that need consistent, branded output at volume. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Documint.
Create a document from a template
Create a document by merging a template with the data for a specific customer or order.
List documents already generated
List generated documents to confirm one exists before regenerating it unnecessarily.
Confirm before deleting a template
Require approval before deleting a template, since active document generation may depend on it.
6 Documint actions, graded by risk.
Every Documint action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- documint.get_templateGet Template
- documint.list_documentsList Documents
- documint.list_templatesList Templates
write
2Create and change things. Allow, or ask the user first.
- documint.create_documentCreate Document
- documint.update_templateUpdate Template
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- documint.delete_templateDelete Template
Documint in three steps.
- 01Your users connect DocumintThey add their Documint api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Document” can wait for the user, and “delete Template” can be denied outright.
- 03Any agent can actYour agent calls Documint through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('documint', { read: 'allow', write: 'ask', // create_document destructive: 'deny', // delete_template }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Documint connects.
Users add their Documint api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Documint connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Documint from any agent.
Documint and Arc0, answered.
Can I use Documint with Claude, ChatGPT or Cursor?
Yes. Connect Documint to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Documint actions you allow.
How do users connect Documint?
Users add their Documint api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Documint actions can my agent take?
6 in total: 3 read, 2 write and 1 destructive, such as “create Document”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Documint?
Yes. Actions like “delete Template” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Documint too?
Yes. The same Documint connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Documint into your agent.
Your users connect Documint once, under your brand. Your agent gets 6 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan