A signing tool built around the document you already have
Most e-signature products make you rebuild your contract in their editor. Here the document is the editor: you mark fields with short typed glyphs, and the rest is automatic.
1. Mark your document with glyphs
Type a glyph wherever a signer should put something. The number says which signer; the letter says what. Glyphs are usually typed in white, 1-point text so they vanish on the page but stay in the file.
| Glyph | Places | Notes |
|---|---|---|
\s1\ | Signature of signer 1 | Drawn or typed signature image, sitting on the line. |
\i1\ | Initials of signer 1 | Small initials image; use one per page for "initial each page". |
\n1\ | Printed name | The name the signer types. |
\d1\ | Date signed | Filled automatically when that signer completes. |
\t1:Job title\ | Text field with a label | Required unless the label ends with !, e.g. \t1:Phone!\. |
\c1\ | Checkbox | Required tick unless written \c1!\. |
\s2\, \d2\… | Second signer | Up to 99 signers on a paid plan (one on Free); each is invited in order. |
Word documents are converted to PDF on our server before glyphs are read, so what the signer sees is what you see. PDFs are used as-is. Scanned images have no text and therefore no glyphs; export from the original document instead, or place the fields by hand.
Or place the fields by hand
On a paid plan, a document needs no glyphs at all. Upload it as it is, even a scan, and every page opens on screen: drag signature, initials, name, date, text and checkbox fields onto it, move and resize them, and give each one to a signer. Fields found from glyphs open in the same editor, so you can nudge those too. It works for a one-off pact and for a template you reuse.
2. Send
Create a pact from a template or a one-off upload, add recipients in signing order (one signer on the Free plan, several on a paid plan, and any number of CCs), write a short message, and send. Each signer receives a private link when it is their turn. You can resend, void, or watch progress from the dashboard.
3. Sign
The signer sees the document as page images on any device, fills in their fields, draws or types a signature, reads a short consent to electronic records, and submits. Links are single-purpose codes that expire when the pact lapses, and repeated bad guesses from an address are blocked.
4. Keep the proof
When the last signer finishes, every field is stamped into the PDF and the pact is sealed with its sigil, a certificate of completion: the SHA-256 hash of the document that was sent and of the signed result, each signer's name, email, IP address, browser, consent version and timestamps, and the full event log. Both PDFs go to every signer, every CC and you.
Your own domain
Pro includes one custom domain and Business three, and any plan can add more for a small monthly fee. Bind sign.yourcompany.com to your account by adding one DNS record. Signing links, the signer pages and invitation emails then carry your name, logo and colour. Your dashboard stays here.
API and MCP
Every account can create API keys; using them needs the Pro or Business plan. The JSON API creates templates and pacts, sends and voids them, and returns signed documents. The same key powers an MCP server, so an assistant such as Claude can prepare and send pacts for you. Guides, every endpoint and examples are in the developer docs; keys are on the API page.
curl -H "Authorization: Bearer sgk_…" \
-F file=@agreement.pdf -F name="Consulting agreement" \
https://api.signwithsigil.com/v1/templates