D6E D6E
Back to developers
SignKit

SignKit guide

Deploy a SignKit instance, claim its first owner, and send an agreement from the browser.

The SignKit core is open source under AGPL-3.0-only.

1. Deploy the instance

Authenticate Wrangler, inspect the plan, and provide the registered d6e-auth client credentials through a protected stdin file. create-signkit generates the three internal secrets and installs all five with the deployment.

Inspect the plan

pnpm dlx create-signkit@0.1.2 --cloudflare plan --account-id <32-hex-account-id>

Prepare the OAuth input file (0600)

cat <<'EOF' > /secure/path/signkit-oauth.json
{
  "D6E_AUTH_CLIENT_ID": "<id>",
  "D6E_AUTH_CLIENT_SECRET": "<secret>"
}
EOF
chmod 0600 /secure/path/signkit-oauth.json

Deploy

pnpm dlx create-signkit@0.1.2 --cloudflare deploy \
  --account-id <32-hex-account-id> \
  --email-from ops@example.com \
  --domain sign.example.com \
  --bootstrap-owner-email owner@example.com \
  --yes < /secure/path/signkit-oauth.json

2. Claim the first owner

Sign in with the address passed to --bootstrap-owner-email, then claim the empty instance. Only that verified address can complete the initial claim.

3. Send an agreement

  1. Create a new agreement.
  2. Upload PDF or DOCX, or edit the Markdown source; preview and commit the revision.
  3. Add recipients, roles, language, and routing order, then mark the recipient list ready.
  4. Place signer fields on the rendered pages and publish the revision.
  5. Review the final confirmation, send, and monitor delivery and recipient decisions.

Use it from an AI agent

Install the SignKit skills (signkit-api and signkit-cli) and an AI agent can handle agreements through the API and the CLI. The CLI operates agreements through the API. A separate create-signkit CLI installs and upgrades a server.

Install the skills

npx skills add https://github.com/d6e-ai/signkit

Reference