Skip to content

Changelog

Each entry says what is new, how to use it, whether your prompt needs regenerating, and which requirements are affected.

Plans

Live signatures on the Free plan

The Free plan now includes 10 live signature events a month on one verified domain, next to the full test mode. No card.

What is new

  • Free covers 10 live signatures a month. If you use all 10 in a month, the account locks until you upgrade to a paid plan. It does not unlock at the start of the next month. Past the limit, new live signatures can be refused, so upgrade before you get there. An account that stays under 10 is never locked and starts the next month with 10 again.
  • Real records. A live record on Free gets the outside RFC 3161 timestamp, checkpoints, the public anchor, a public verification page, the signer copy by email, the evidence report, and the evidence package.
  • Paid plans add. Certificates for live records, SMS codes, L3 on Unlimited and above, more seats, more webhook endpoints, and the EU region.

How to use it

  1. Verify your domain and add your organization details.
  2. Create a live key. There is no checkout.

Prompt update

Prompts generated before this change keep working. The API calls are the same in test mode and live.

Compliance note

No rule pack changes. A live record on Free is sealed the same way as a live record on a paid plan.

v1.0

Version 1.0

The first general release: rule packs, the ceremony API and browser SDK, sealed evidence you can verify offline, on-request certificates, customer-supplied material, the prompt generator, and the guidance service.

What is new

  • Rule packs. U.S. Federal, seven U.S. state packs (California, New York, Florida, Texas, Delaware, Virginia, Massachusetts), and separate EU, UK, and Swiss packs, selectable in any combination on a profile. Read the catalogue at GET /v1/jurisdictions and dry-run a selection with POST /v1/jurisdictions/resolve. State packs run in test mode in this release. Each goes live once counsel admitted in that state has reviewed it.
  • Ceremony API. Register document versions with POST /v1/documents/{id}/versions, create a session with POST /v1/sessions, and read the required steps and applied rules from the response.
  • Browser SDK. @esigncomply/browser is headless. EsignComply.attach, presentDocument, observeAssent, and complete report the ceremony from the elements you built.
  • Evidence sealing with receipts. Each live record is hashed, chained per domain, and sealed with an ES256 receipt you can store in your own database. Fetch it at GET /v1/records/{id}/receipt.
  • RFC 3161 timestamps and Merkle checkpoints. An external authority timestamps each live record hash asynchronously. Ledger entries are batched into signed regional checkpoints every 60 seconds, readable at GET /v1/log/checkpoint and GET /v1/log/proof.
  • Evidence reports and packages. GET /v1/records/{id}/report returns the PDF evidence report and GET /v1/records/{id}/evidence the package, which the open-source esigncomply-verify checks with no network access. Both are included in every paid plan.
  • On-request certificates. POST /v1/records/{id}/certificates issues a Contemporaneous Record Statement for a timestamped live record. POST /v1/certificates/quote returns the charge first, and a request that would incur a charge must carry confirm_charge: true.
  • Customer-supplied material. Send free text, JSON, and files through POST /v1/supplements. Each item is sealed with our receipt time and labelled customer-supplied.
  • Prompt generator. The dashboard wizard and POST /v1/prompts/generate turn your use cases, regions, signer types, and stack into one prompt with four fixed headings: Required for the record, Your obligations, Recommendations, and What you can send us.
  • Guidance service. Rules, obligations, recommendations, and notices ship as data on their own release train. Read them at GET /v1/guidance/notices, GET /v1/guidance/releases, and GET /v1/profiles/{id}/guidance.

How to use it

  1. Create an account and generate a prompt. The account is free, and test mode needs no card or domain.
  2. Paste the prompt into your AI coding tool. Your server creates sessions with a test key and the SDK attaches to your controls. Test keys work on localhost.
  3. Record a test signature and confirm the record on your server before granting access. The quickstart walks through each call.

Prompt update

This is the first release of the prompt library. The core, us, eu, signature, assurance, records, and guidance blocks ship at their first version. No prompt change needed.

Compliance note

First release. It introduces the Federal requirement set, the EU, UK, and Swiss requirement sets, and the state rule sets for California, New York, Florida, Texas, Delaware, Virginia, and Massachusetts. Under requirement SP-6, state packs stay in test mode until counsel review.

Record your first test signature.

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: /changelog.md