Skip to content
Moving off Ironclad Clickwrap? Start here

The e-signature and clickwrap API for DIY builders.

Vibe code the signing flow in your own UI. We give your AI tool the rules and keep the record, so it doesn't live in a table you can edit.

Free plan: 10 live signatures a month and a full test mode. No card required.

POST /v1/sessions

Add a signup clickwrap to the app you already have

Create a session on your server. Attach the SDK to your own checkbox and button. The API stores the record before responding and returns a signed receipt. The external timestamp and public anchors follow asynchronously.

import { EsignComply } from "@esigncomply/browser";

const sessionResponse = await fetch("/api/ceremony", { method: "POST" });
if (sessionResponse.ok === false) throw new Error("Unable to create ceremony");
const { clientToken, documents } = await sessionResponse.json();
// clientToken is a short-lived esc_ct_... token, not a secret API key.

const ceremony = await EsignComply.attach({ clientToken });

await ceremony.presentDocument({
  versionId: documents[0].version_id,
  mode: "hyperlink",
  link: document.querySelector("#tos-link"),
});

await ceremony.presentDocument({
  versionId: documents[1].version_id,
  mode: "hyperlink",
  link: document.querySelector("#privacy-link"),
});

ceremony.observeAssent({
  region: document.querySelector("#assent"),       // notice text, links, checkbox, button
  checkbox: document.querySelector("#agree"),
  submit: document.querySelector("#create-account"),
});

// Call this from the real submit handler, after the SDK records trusted intent.
async function finishSignup() {
  const result = await ceremony.complete(); // { recordId, receipt, verifyUrl }
  await confirmSignupOnYourServer(result.recordId); // Your authenticated server route
}

The signup example uses an L1 profile with no extra required steps and test versions of both documents.

Tell your AI tool exactly what to build

Pick your use case, regions, signer types, and stack. Get one prompt. Paste it into Cursor, Claude Code, v0, Lovable, Bolt, or Replit.

  1. 01
    ChoosePick a use case and signer type, then choose jurisdiction packs in any combination.
  2. 02
    PasteCopy the prompt or open it in Cursor. Your tool reads the applied rules and wording from the session.
  3. 03
    CheckRun a conformance check over your test records and see what is missing before you go live.
Generate a prompt
esigncomply-prompt.md
## Required for the recordCreate every session on the server with the secret key. Send only client_token to the browser.Read required_steps from the session and satisfy each one. Do not hard-code steps.
## Your obligationsDuties the law places on your company, listed so your team can handle them.
## RecommendationsSuggestions. Ask the developer before applying any that changes the product.
## What you can send usOptional reports your company may file. Each is sealed on receipt and marked as supplied by you.
The conformance check tests everything under the first heading.
Why not just log it in Supabase

Your acceptances table works. It is also yours to edit.

That is the problem with doing this part yourself. In a dispute, you have to explain who could change it and how you know the record is intact.

public.acceptances

Your table

  • Written by your own code, on your own server.
  • Editable by anyone with database access.
  • No independent record of what the interface presented and what the software received.
rec_Z4m8 · receipt

Our record

  • In a direct browser ceremony, the signer's browser reports events straight to us, outside your server.
  • We add our server time, bind the record to the exact document version, and seal it with a key held in a separate cloud account.
  • We obtain an external RFC 3161 timestamp for the live record. Export the evidence package to verify its integrity and timestamp offline.

Keep your table. Store our receipt in it.

Why a third party keeps the record

The part you shouldn't DIY: the record

Esign Comply captures direct browser evidence and seals and stores live records separately from the parties to the agreement.

Recordrec_Z4m8
simple · L1
RecordedWritten durably, receipt signed with ES256
TimestampedExternal RFC 3161 token over the record hash
AnchoredPublic anchor pending
Checkbox changed by a trusted user eventobserved
Terms of Service, version dv_3kT9observed
Server time 2026-11-21T15:03:20.291Zobserved
Signer email dana@example.orgasserted
record_hash sha256:5be7…example record
01

Direct browser channel

In a direct browser ceremony, events go straight to Esign Comply.

02

Our own seal

Receipts signed with ES256, with hardware-backed keys held in a separate AWS account.

03

External timestamps

An external RFC 3161 authority timestamps each live record hash asynchronously.

04

Append-only ledger

Hash-chained per domain, batched into signed regional Merkle checkpoints every 60 seconds.

05

Write-once copy

Protected checkpoint bundles are kept in write-once storage.

06

Verify offline

Check an exported package with the open-source esigncomply-verify, without an account.

How sealing works

Annual pricing per domain

Free

$0

10 live signatures a month on one domain. Full test mode. No card.

Starter

$200 per year

2,000 live events. No certificates included; $20 each when issued.

Unlimited

$1,200 per year

Unlimited events, fair use. 25 certificates per subscription year, then $20 each.

Enterprise

from $10,000 per year

Unlimited certificates.

A bundle of up to 10 documents accepted together is one event. Test events never count. See pricing

Questions developers ask

How do I add a clickwrap to my Next.js app?

Create a session on your server with POST /v1/sessions, then attach the browser SDK to your own checkbox and button. The SDK reports the ceremony from the signer's browser, and the API stores the record and returns a signed receipt you keep next to the user.

View the Next.js example

Can I build e-signatures with Cursor, Claude Code, or Lovable?

Yes. Pick your use case, regions, signer types, and stack, and get one prompt to paste into Cursor, Claude Code, v0, Lovable, Bolt, or Replit. Your tool builds the flow in your own UI, and a conformance check over your test records shows what is missing before you go live.

Generate a prompt

Can I build my own DocuSign alternative?

Yes. Vibe code the whole product: upload a document, email each signer a link, and they sign inside your app. Your AI tool builds the screens, and Esign Comply gives it the rules and keeps the independent record of every signature.

Build your own DocuSign

Why isn't a row in my database enough?

Because the company relying on the row also controls it. In a direct browser ceremony Esign Comply receives the events separately, then seals and externally timestamps the live record. Anyone you give the evidence package to can check its integrity and timestamp offline.

Why a third party keeps the record

Is a DIY clickwrap legally binding?

Electronic signatures and clickwraps are recognized under the U.S. ESIGN Act and state UETA laws: a signature cannot be denied legal effect just because it is electronic. What matters is clear notice, an unmistakable act of assent, and a record of both. Esign Comply gives your AI tool those rules and keeps that record.

The U.S. rules we apply

Is there a free plan?

Yes. The Free plan includes 10 live signature events a month on one verified domain, plus a full test mode with 500 test events a month. No card is required. Starter is $200 per year for 2,000 live signature events.

See pricing

Build the signing flow yourself. Leave the record to us.

Get started

Free plan: 10 live signatures a month and a full test mode. No card required.

Working with an AI tool? This page is also available as Markdown: /index.md