AnySign Signing
Seamless signing that works anywhere.
Place the fields, name the signers, send. They consent, verify and sign on any device, in their language. You get a sealed PDF, a Certificate of Completion, and an audit trail that proves every step.
TRY IT
Place a field. Sign it. Watch it seal.
Pick a field type, click the page to place it for Ada, then sign as her. The page is the same shape a real signer sees.
Field to place
Click anywhere on the page to drop a signature field for Ada. Up to six.
Then
- fields placed
- consent recorded
- fields signed
- sealed · chain_valid
Consulting agreement · page 4 of 4
THE LOOP
From draft to sealed, without the back-and-forth.
What a signature needs to survive an argument.
Anyone can draw a squiggle on a PDF. Holding up later is about what was recorded around it.
Fields on any PDF
Drag signature, initials, date and text fields onto the page. Signers draw or type, and the result is embedded in the executed PDF.
Sequential or parallel
Everyone at once, or one after another in the order you set. Each signer gets their own tokenized link and their own hosted page.
Consent before the first field
ESIGN and UETA aligned disclosure, shown and accepted before anything is signed, stored verbatim with timestamp, IP, user agent and language.
AES with SMS verification — coming soon
A per-signer one-time code over SMS for high-stakes documents, written into the audit trail beside the signature. Coming soon on the Business plan; signing today is SES.
Five languages, in person too
The signing flow runs in English, German, French, Spanish and Japanese, and works for in-person signing on a device you hand across the table.
Sealed, chained, certified
Every view, consent and signature hashes the event before it. The executed PDF is PAdES-sealed and locked with DocMDP, and a Certificate of Completion travels with it.
BUILT TO BE ARGUED OVER LATER
What was recorded around the signature.
A signature is only as strong as the evidence beside it. AnySign records the disclosure the signer accepted, who they proved they were, and every event in between, then seals the document so nothing after the fact can move.
- ESIGN and UETA aligned consent, stored verbatim per signer
- AES: a per-signer SMS one-time code written into the trail beside the signature — coming soon on Business, not yet available
- PAdES certification signature, DocMDP lock, Certificate of Completion attached
FROM CODE, OR FROM YOUR AI
Your agent can send the envelope.
Every envelope is a resource on /v1, and the same actions are MCP tools. Connect Claude, ChatGPT or Cursor through OAuth 2.1, ask for the consulting agreement to go out to Ada, and let a signed webhook tell your stack the moment it is sealed and chain-valid.
- Create, send and fetch envelopes on /v1; templates fill fields from code
- MCP server: list, fetch, create and send envelopes; list templates. Nothing destructive.
- HMAC-signed webhooks for viewed, consented, signed and completed
npm i @anysign/sdkSend the consulting agreement to [email protected]
- list_templatesConsulting agreement
- create_envelope[email protected] · signer
- send_envelopeenv_8f14e2
envelope.completed · sealed, webhook delivered
Works from
- Claude
- ChatGPT
- Cursor
- Gemini
- Copilot
- Perplexity
Who sends the same invoices, agreements and files every week.
- AccountantsSend draft accounts, tax packs and fee proposals as links only named clients can open, with an expiry date, one-click revoke and a log of every view.See the use case
- BrokersShare lender packs, policy documents and client financials as links tied to named addresses, with an expiry you set, instant revoke and a full view log.See the use case
- RecruitersSend CVs, offer letters and references as links only the named hiring team can open, with an expiry, one-click revoke and a log of every open.See the use case
Signing is free while AnySign is in beta: 30 envelopes a month, with templates, reminders, bulk send and sequential flows. Beta refers to the pricing, never the legal weight of a signature.
What the beta includesSigning questions.
Are the signatures legally binding?
Yes. Under the ESIGN Act and UETA, an electronic signature has the same legal effect as one in ink. AnySign captures explicit intent and ESIGN and UETA aligned consent before signing, records it verbatim per signer, and seals the executed PDF with a PAdES certification signature. Signature levels (SES, AES) are tracked per envelope, so if a signature is ever challenged the evidence is already there. A few categories — wills, most family law papers, anything needing notarisation — sit outside those laws: see the e-signature legality page.
Does a signer need an account?
No. They open their link, read the disclosure, consent, and sign. AES, which adds a one-time code to their phone, is coming; signing today is SES end to end.
Can I embed signing inside my own product?
Yes. POST /v1/envelopes/{id}/signing_sessions returns an embedded signing session you can show inside your app instead of sending an email.
What about sending the same document to a hundred people?
Bulk send takes a CSV and creates one envelope per row from a template. It is included from the Pro plan up.
Is the audit engine weaker on cheaper plans?
No. Consent capture, the hash-chained trail and the PAdES seal are identical on Free and on Business. Plans change quotas, never the legal weight.