eSignatures for AI agents

eSignatures is an electronic signature platform for building templates, sending contracts, and tracking the signing process to completion, used by sales and legal teams closing agreements. 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.

Connect eSignatures See the 28 actions ↓

DocumentsAPI keyMCP + RESTesignatures.com

AUDIT LOG · ESIGNATURESPOLICY: acme-support

09:41:07 · claude · u_8f2read

esignatures.list_templates

List Templates✓ allowed · 212ms

09:41:08 · claude · u_8f2read

esignatures.get_contract

Get Contract✓ allowed · 164ms

09:41:09 · claude · u_8f2write

esignatures.create_template

Create Template✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

esignatures.delete_template

Delete Template✕ blocked · policy: deny

EVERY ESIGNATURES CALL, ON THE RECORD

01 · USE CASES

What agents do in eSignatures.

Send a contract for signature

Create and send a contract to a signer once the sender confirms the placeholder fields.

Check a contract's status

Get a contract's current status to tell someone whether it has been fully signed.

Confirm before withdrawing a contract

Require approval before withdrawing a contract, since it cancels an agreement already sent to a signer.

02 · ACTIONS

28 eSignatures actions, graded by risk.

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

read

Look things up. Allowed by default.

esignatures.get_contract
Get Contract
esignatures.get_template
Get Template
esignatures.list_templates
List Templates
esignatures.get_contract_content
Get Contract Content
esignatures.get_template_content
Get Template Content
esignatures.list_template_collaborators
List Template Collaborators
esignatures.get_contract_placeholder_fields
Get Contract Placeholder Fields
esignatures.preview_contract_content_update
Preview Contract Content Update
esignatures.preview_template_content_update
Preview Template Content Update

write

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

esignatures.create_template
Create Template
esignatures.update_template
Update Template
esignatures.add_contract_signer
Add Contract Signer
esignatures.send_draft_contract
Send Draft Contract
esignatures.add_contract_signers
Add Contract Signers
esignatures.create_contract_draft
Create Contract Draft
esignatures.update_contract_signer
Update Contract Signer
esignatures.update_contract_content
Update Contract Content
esignatures.update_template_content
Update Template Content
esignatures.create_and_send_contract
Create and Send Contract
esignatures.add_template_collaborator
Add Template Collaborator
esignatures.update_contract_placeholder_fields
Update Contract Placeholder Fields
esignatures.withdraw_contract
Withdraw Contract
esignatures.duplicate_template
Duplicate Template
esignatures.resend_sign_request
Resend Sign Request
esignatures.invite_template_collaborator
Invite Template Collaborator

destructive

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

esignatures.delete_template
Delete Template
esignatures.delete_contract_signer
Delete Contract Signer
esignatures.remove_template_collaborator
Remove Template Collaborator

03 · HOW IT WORKS

eSignatures in three steps.

01Your users connect eSignaturesThey add their eSignatures api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, writes like “create Template” can wait for the user, and “delete Template” can be denied outright.
03Any agent can actYour agent calls eSignatures 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('esignatures', {
  read: 'allow',
  write: 'ask',        // create_template
  destructive: 'deny',  // delete_template
})

# 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 eSignatures connects.

Users add their eSignatures 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 eSignatures 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 eSignatures from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

eSignatures and Arc0, answered.

Q01

Can I use eSignatures with Claude, ChatGPT or Cursor?

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

Q02

How do users connect eSignatures?

Users add their eSignatures 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 eSignatures actions can my agent take?

28 in total: 9 read, 16 write and 3 destructive, such as “create Template”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in eSignatures?

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.

Q05

Can my own backend call eSignatures too?

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

Get started

Plug eSignatures into your agent.

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

Connect eSignatures Browse all apps →

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