Contractbook for AI agents

Contractbook manages the full lifecycle of contracts, from drafting and sending to signing and storage, keeping legal paperwork organized in one place. 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.

DocumentsAPI keyMCP + RESTcontractbook.com
AUDIT LOG · CONTRACTBOOKPOLICY: acme-support
09:41:07 · claude · u_8f2read
contractbook.list_documents
List Documents✓ allowed · 212ms
09:41:08 · claude · u_8f2read
contractbook.get_document
Get Document✓ allowed · 164ms
09:41:09 · claude · u_8f2write
contractbook.create_document_from_template
Create Document From Template✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
contractbook.delete_document
Permanently Delete Document✕ blocked · policy: deny
EVERY CONTRACTBOOK CALL, ON THE RECORD
01 · USE CASES

What agents do in Contractbook.

01

Create a contract from a template

Create a new contract from a saved template, ready to send out for signature.

02

Check a document's status

Check a document's status to see whether all parties have signed yet.

03

Confirm before permanently deleting a document

Confirm before permanently deleting a document, since the action cannot be undone.

02 · ACTIONS

9 Contractbook actions, graded by risk.

Every Contractbook action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

6

Look things up. Allowed by default.

  • contractbook.get_document
    Get Document
  • contractbook.get_template
    Get Template
  • contractbook.list_documents
    List Documents
  • contractbook.list_templates
    List Templates
  • contractbook.list_automations
    List Automations
  • contractbook.get_document_pdf_link
    Get Document PDF Link

write

2

Create and change things. Allow, or ask the user first.

  • contractbook.update_document
    Update Document
  • contractbook.create_document_from_template
    Create Document From Template

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • contractbook.delete_document
    Permanently Delete Document
03 · HOW IT WORKS

Contractbook in three steps.

  1. 01Your users connect ContractbookThey add their Contractbook api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Document From Template” can wait for the user, and “permanently Delete Document” can be denied outright.
  3. 03Any agent can actYour agent calls Contractbook through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('contractbook', {
  read: 'allow',
  write: 'ask',        // create_document_from_template
  destructive: 'deny',  // delete_document
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Contractbook connects.

Users add their Contractbook 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 Contractbook 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
05 · WORKS WITH

Use Contractbook from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Contractbook and Arc0, answered.

Q01

Can I use Contractbook with Claude, ChatGPT or Cursor?

Yes. Connect Contractbook 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 Contractbook actions you allow.

Q02

How do users connect Contractbook?

Users add their Contractbook 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.

Q03

Which Contractbook actions can my agent take?

9 in total: 6 read, 2 write and 1 destructive, such as “create Document From Template”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Contractbook?

Yes. Actions like “permanently Delete Document” 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.

Q05

Can my own backend call Contractbook too?

Yes. The same Contractbook connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Contractbook into your agent.

Your users connect Contractbook once, under your brand. Your agent gets 9 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan