eSignatures.io for AI agents

eSignatures.io lets businesses send and sign mobile-friendly contracts over the web, with templates for repeatable agreements like service contracts, leases, and onboarding paperwork. 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.io See the 17 actions ↓

DocumentsAPI keyMCP + RESTesignatures.io

AUDIT LOG · ESIGNATURES.IOPOLICY: acme-support

09:41:07 · claude · u_8f2read

esignatures_io.list_templates

List Templates✓ allowed · 212ms

09:41:08 · claude · u_8f2read

esignatures_io.get_contract

Get Contract✓ allowed · 164ms

09:41:09 · claude · u_8f2write

esignatures_io.create_signer

Create Signer✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

esignatures_io.delete_signer

Delete Signer✕ blocked · policy: deny

EVERY ESIGNATURES.IO CALL, ON THE RECORD

01 · USE CASES

What agents do in eSignatures.io.

Send a contract to a signer

Send a contract created from a template to a named signer for their signature.

Preview a contract as a PDF

Generate a PDF preview of a contract so a reviewer can check it before it goes out.

Confirm before withdrawing a contract

Require approval before withdrawing a sent contract, since it cancels the pending signature request.

02 · ACTIONS

17 eSignatures.io actions, graded by risk.

Every eSignatures.io 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_io.get_contract
Get Contract
esignatures_io.get_template
Get Template
esignatures_io.list_templates
List Templates
esignatures_io.list_template_collaborators
List Template Collaborators

write

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

esignatures_io.create_signer
Create Signer
esignatures_io.update_signer
Update Signer
esignatures_io.create_contract
Create Contract
esignatures_io.create_template
Create Template
esignatures_io.update_template
Update Template
esignatures_io.send_contract_to_signer
Send Contract to Signer
esignatures_io.add_template_collaborator
Add Template Collaborator
esignatures_io.copy_template
Copy Template
esignatures_io.withdraw_contract
Withdraw Contract
esignatures_io.generate_contract_pdf_preview
Generate Contract PDF Preview

destructive

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

esignatures_io.delete_signer
Delete Signer
esignatures_io.delete_template
Delete Template
esignatures_io.remove_template_collaborator
Remove Template Collaborator

03 · HOW IT WORKS

eSignatures.io in three steps.

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

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

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

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

eSignatures.io and Arc0, answered.

Q01

Can I use eSignatures.io with Claude, ChatGPT or Cursor?

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

Q02

How do users connect eSignatures.io?

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

17 in total: 4 read, 10 write and 3 destructive, such as “create Signer”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in eSignatures.io?

Yes. Actions like “delete Signer” 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.io too?

Yes. The same eSignatures.io 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.io into your agent.

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

Connect eSignatures.io Browse all apps →

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