Skip to content

Agents overview

DocTransit is built so AI agents can create and send contracts while humans sign via email or sign links.

Path of least resistance

  1. Create an API key in the app: Developer → API Keys
  2. Install MCP (Cursor) or the CLI
  3. Create from a template → add signers → send → MCP wait_for_document (or a webhook) until completed

Surfaces

SurfacePackage / URLBest for
MCP@doctransit/mcpCursor, Claude Desktop
CLI@doctransit/cliShell agents, CI
SDK@doctransit/sdkCustom Node agents
RESThttps://api.doctransit.com/v1Any language

Auth

http
Authorization: Bearer dt_…

Also accepted: X-DocTransit-ApiKey: dt_…

Safety

  • send_document / CLI docs send require explicit confirmation
  • Prefer draft + review before send
  • API access is gated on Business+ plans (UCP features.api)
  • documents:sign is not on default API keys. Grant a Signing Mandate in the app (Developer → Signing Mandates). L1 requires the principal to confirm each signature. L2 auto-signs in-scope documents and emails the principal after every apply. The agent is never a legal party.

Signing mandates

A mandate is an open authorization: the registered user consents once, with email OTP, that a specific API key may apply their stored signature later. It does not sign any document by itself. Revoke anytime; completed documents stay signed.

Full flow, flags, widgets, and errors: Signing with an agent.

Agents can GET /mandates or use MCP list_mandates. After a mandate exists: MCP request_sign (L1 confirm) or sign_as_principal (L2 only). There is no silent sign_document tool.

Agent Contacts and offers

An Agent Contact is mutual recognition between two principals (invited → active → revoked). It is not a signature. After both sides are active, either agent can propose_contract a sent document. The receiving agent accept_offer: in-policy L2 applies the principal’s stored signature; L1 or human_signature_required escalates to a confirm link (Signing with an agent). The contract is always principal ↔ principal.

The wire format is DASP (AP2 open/closed mandate + receipt language). DocTransit is the settlement layer: hash, stored appearance, disclosed certificate.

Transfers

Share Drive files, or lock them behind a document (sign-to-unlock). Recipients get a claim link that works with or without an account. See Transfers.