LaunchKit · 2026
Back to Skills

saysigned

> **E-signatures for AI agents.** Legally binding under ESIGN Act & UETA Section 14.

0
346 downloads
by @klsv

Setup & Installation

openclaw skills install @klsv/saysigned

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install saysigned

Version History

v1.0.1Feb 20, 2026 - Version note by skill developer:

### Version 1.0.1 — Changelog - Human confirmation is now required before making any MCP client config changes (such as adding API keys or restarting the client). - All setup steps that modify system configuration now instruct to show the pending change and require explicit user approval before proceeding. - Publisher, homepage, documentation links, and TLS requirements added to documentation for improved clarity. - Minor edits for clarity and emphasis on human-in-the-loop control for sensitive actions.

What This Skill Does

SaySigned lets AI agents create, send, and sign legally binding contracts via REST API or MCP. Signatures are valid under the ESIGN Act and UETA Section 14. Two modes: API for agent-to-agent signing, Email for sending consent links to humans.

Handles the full signing lifecycle natively in agent workflows, including legal compliance, audit trails, and RFC 3161 timestamping, without routing through a human-managed e-signature platform.

When to use it

  • Collecting NDA signatures before sharing confidential project details
  • Automating service agreement signing between two AI agents
  • Sending a contract to a human employee for review and e-signature via email
  • Verifying the cryptographic integrity of a completed signed envelope
  • Tracking signature status across multiple recipients in a multi-party deal

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Have Acme Corp and Beta Inc sign a mutual NDA

AGENT
  1. 1Calls saysigned_create_envelope with template_id 'nda_mutual_v1' and party names, dates, and governing state as variables
  2. 2Calls saysigned_send_envelope to dispatch the draft, receiving access tokens for each recipient
  3. 3Calls saysigned_sign for each recipient using their access token and full name
  4. 4Calls saysigned_verify to confirm the hash chain and RFC 3161 timestamp are valid
OUTPUT

Completed envelope with both signatures, a DigiCert-anchored timestamp, and a verifiable audit trail

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

SaySigned API key (obtained by calling saysigned_register — shown once, must be saved immediately)