When a checkbox is not enough

When an AI agent accepts terms for you

An agent negotiates a vendor contract overnight, agrees to a freelancer's rate, or accepts a service's terms so it can finish a task. The person wakes up to a done deal. If that deal is later questioned, by the person, the other party, or a court, the question is not whether software can agree to things. It is whether anyone can show what was agreed, when, and that the record has not been quietly edited since by whoever runs the system. That is a records problem, and it is the one Signathing was built around.

The problem is not the signature, it is the trust

When a person signs, they remember doing it. When an agent signs, the person is relying entirely on the record. And the record is held by the signing service, which has every incentive, in a dispute, to be believed. A record that only the service can vouch for is a weak place to stand when an agent has committed you to something.

What a stranger needs is a record they can check without trusting the service or the agent: a copy of the agreement whose fingerprint is public, a timestamp that a third party anchored, and a log of events that cannot be rewritten without the rewrite showing.

What the evidence log provides

Every signing event on Signathing, sent, viewed, signed, completed, is appended to a public hash chain. Each entry commits to the event's private details through a hash without publishing them. Each day's chain is sealed, archived with the Internet Archive, timestamped with OpenTimestamps on the Bitcoin blockchain, and mirrored to a public GitHub repository. Each sealed day also has a Merkle root, so a single entry can be proven part of the day from the evidence package alone, offline.

The agent, or the person, or the other party, downloads the evidence package and runs an open, dependency-free verifier script. It recomputes every hash from the package, checks each entry against the public log, and checks the day's timestamp against Bitcoin. Nobody has to take Signathing's word for anything.

What the person should set up before letting an agent sign

Decide what the agent may agree to and for how much, and write that into the agent's instructions. Have the agent send agreements through a service that produces a verifiable record rather than a screenshot. Make the person a view-only recipient or a cc on every document so a certified copy lands in a human inbox the moment it is signed. And keep the evidence packages, which are the record that outlives the agent, the session and the service.

For the other party

If you are the human on the other side of an agent, the same record protects you. The agreement the agent signed is fingerprinted, timestamped and public in its hashes. If the agent's principal later says the agent exceeded its authority, you have a certified copy with a verification code and a chain entry that proves when it was signed. Authority is a question between the principal and their agent; the record of what was signed is not in dispute.

Common questions

Can an AI agent sign a document through Signathing?
An agent can send documents, place fields, and collect signatures through the REST API or the MCP server, and it can sign as a recipient when its principal has set that up. Every action is a chain entry in the public evidence log.
Is an agreement accepted by an agent recognized?
Electronic signatures and electronic records are recognized under the federal ESIGN Act and state UETA laws, which also address electronic agents acting for a party. Whether an agent had authority in a given case is a question of fact between the principal and the agent; the record of what was signed and when is what Signathing supplies.
How does someone verify the record without trusting Signathing?
Download the evidence package and run the open verifier. It recomputes every hash, checks each entry against the public log and the GitHub mirror, walks the Merkle path to the sealed day's root, and checks the OpenTimestamps proof against Bitcoin.
What does the public log reveal about my agreement?
Only hashes, timestamps and event types. No names, emails, documents or terms. The private details are in the evidence package, which only the parties hold.
Is this free for agents too?
Sending and signing are free for people. The API and MCP server include 100 documents a month free with no card, then prepaid per document.

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