DocTransit Docs

Appearance

Cookbook: agent applies your signature ​

The agent never becomes a party. You grant a mandate; DocTransit applies your stored mark. Details: Signing with an agent.

Once ​

  1. Save a signature under Settings → My Signature
  2. Create an API key (Developer → API Keys)
  3. Grant a Signing Mandate for that key (Developer → Signing Mandates)
    • L1 — you confirm each apply at /sign-request/{token}
    • L2 — in-policy auto-sign + email notify (25/day)
  4. Confirm the email OTP
  5. Point MCP or the CLI at the key (0.3+ for mandate tools)

L1 — confirm each mark ​

create_document (you as a signer) → send_document
request_sign
open confirm_url → Confirm and apply my signature
bash
doctransit docs create --template TEMPLATE_ID \
  --signer "You <you@example.com>" --name "L1 example" --send
doctransit docs request-sign DOC_ID --reason "policy match"

L2 — in-policy apply ​

Requires an L2 mandate and l2_signing enabled (GET /v1/flags).

create_document (you as a signer) → send_document
sign_as_principal
bash
doctransit docs sign DOC_ID --reason "in-policy NDA"

An L1 mandate calling sign / sign_as_principal returns confirmation_required. Use request_sign instead.

Two agents ​

After both principals have an Agent Contact and a mandate: propose_contract → accept_offer. L2 accepts in policy; L1 or human_signature_required escalates to a confirm link.