When a checkbox is not enough

For software teams: swap the checkbox for a signing step

Most products record agreement as a boolean: terms_accepted = true, with a timestamp if someone thought of it. That is fine for a newsletter signup. It is thin for a personal guarantee, a contractor agreement, a change of terms, a payment authorization, or anything a customer might one day deny. A signing step records the person, the document as it stood, the consent to sign electronically, the time and device, a certified PDF both sides receive, and an entry in a public audit log. The swap is an API call.

What a checkbox does not record

Which version of the terms was shown. Whether the person could see the whole document. Who the person actually was, beyond a session. That they intended to sign rather than clear a modal. And a copy they received. When a user says they never agreed, a row with a true in it is the whole of your evidence, and you are the only one holding it.

A signing step gives the user a document to read, a consent step, a signature, and a certified copy with a verification code. It gives you an evidence package and a chain entry in a public log that you do not control. The difference shows up exactly once: the day someone disputes it.

Where the swap pays for itself

Guarantees and credit terms in B2B onboarding. Contractor and vendor agreements in a marketplace. Recurring payment authorizations. Changes of terms for existing customers. Policy acknowledgments for a workforce. Anything a regulator or a counterparty might ask you to produce later. For the low-stakes click-through, keep the checkbox; nobody needs a certified copy of a cookie banner.

How the integration looks

Create a template once with your document and its fields, or send a generated PDF per transaction. When the moment comes, one API call sends the document to the user by email or text, or returns a signing link you embed in your flow. A webhook tells you when it is viewed, signed and completed. The certified PDF and the evidence package are available by API. The MCP server exposes the same operations to an AI agent in four tool calls. The API is free for 100 documents a month with no card, then prepaid per document.

What your users see

A link, a document they can read, a short consent statement, a signature they type or draw, and a certified copy in their inbox. No account, no app. The step adds a minute to the flow where it matters and nothing where it does not. Your records gain a chain entry per event in a public log that is sealed daily, mirrored, and timestamped on Bitcoin, which is a sentence you cannot say about a boolean.

Common questions

Is a checkbox not a valid electronic signature?
A click can be an electronic signature when the law's elements are met. The question is what you can prove later. A signing step records the person, the document, the consent, the time and a certified copy, which a boolean does not.
Does the user need a Signathing account?
No. Signers open a link and sign in the browser. Only the sender, your system, holds an account and an API key.
Can I embed the signing step in my own UI?
Yes. The API returns a signing link you can open in your flow, and webhooks report each event. The signing page itself is Signathing's, which is what gives the record its independence.
What does the API cost?
100 documents a month are free with no card. Above that, prepaid per document. Sending and signing for people, outside the API, are free with no document cap.
How does an agent use it?
Through the MCP server: send_document, get_document or the completed webhook, get_evidence, then the verifier on what came back. The developers page has the loop.

General information, not legal advice. Laws change and their application depends on the specific facts. Consult a licensed attorney in your state about your own documents.

Free, and not the kind of free with a catch

Unlimited documents, up to 25 signers each, certified PDFs on every one. No trial clock and no card to start.

Start signing free