Sign
SignAmbiguous Sign. E-signature for humans and AI coworkers. ESIGN/UETA-compliant PKI seal on every contract.
Send contracts for signature starting from any PDF or Ambiguous Doc. Recipients sign with a link, no account required. Every signature carries an ESIGN/UETA-compliant PKI seal and a Certificate of Completion stored in your Drive.
Features
Upload a PDF or start from an Ambiguous Doc. Mark signature fields (signature, date, initials) and drag them into position. Send for signing via capability link. Signers never need an account. Track status in real time.
Status tracking
See who has signed and who hasn't. Get notified on each signature event. Resend reminders with one click.
Included from day one
The rest of the Sign feature set. Every item ships in every workspace, for your team and your AI coworkers alike.
Field marking
Drag signature, date, and initials fields onto any position in the document. Assign each field to a signer role.
Capability links
Signers receive a unique link, no account required. Open, review, sign, done. Works on any device.
Certificate of Completion
Every signed document includes a PKI-sealed certificate with timestamps, IP addresses, and signer identity verification.
Start from a Doc
Draft in Ambiguous Docs, then send for signature without exporting. The signed artifact lands back in Drive.
Audit trail
Every view, field fill, and signature event is logged. Export the full trail for compliance records.
ESIGN/UETA-compliant with PKI seal.
Every signed document meets ESIGN and UETA requirements for legally binding electronic signatures. No compliance gaps, no manual audit trail assembly.
PKI seal
Cryptographic signature on every completed document. Tamper-evident: any modification after signing invalidates the seal.
Certificate of Completion
Timestamps, IP addresses, and signer identity for every signature event. Exportable as a standalone compliance record.
Full audit trail
Every view, field fill, and signature event logged with millisecond precision. Export the trail for legal proceedings or compliance reviews.
One product, two ways in
Your agent creates signature requests via MCP or REST. Assign signers, mark fields programmatically, and receive a webhook when all parties sign. The signed PDF with Certificate of Completion lands in Drive automatically.
// Create a signature request via MCP
const result = await mcp.callTool("sign.requests.create", {
document_id: "doc_abc123",
signers: [
{ email: "client@example.com", role: "signer" }
],
message: "Please sign the NDA."
});What your agent can do in Sign
Every action your team takes in Sign, your agent can do the same way.
| Method | Description |
|---|---|
| sign.requests.create | Create a signature request with signers and fields |
| sign.requests.get | Check signing status and signer progress |
| sign.fields.add | Add signature or initial fields to the document |
| sign.requests.send | Send the request to signers via secure link |
| sign.requests.export | Download the signed PDF with certificate |
Imports and exports
Start from any PDF. No signer account required.
Send from an Ambiguous Doc or upload a .pdf. Signers click a capability-link and sign without login. ESIGN/UETA-compliant PKI seal and Certificate of Completion on every signed document. Trigger signature requests programmatically via MCP or REST.
