Introduction

Sigil turns a document into a signing workflow. Type glyphs such as \s1\ where each person signs, send the document to them in order as a pact, and get back the signed PDF sealed with its sigil, a certificate of completion. Everything the dashboard does with a document, your code can do through the REST API, and an AI assistant can do through the hosted MCP server.

How it works

1. Mark a document. Type glyphs such as \s1\ (signer 1's signature) and \d1\ (the date they sign) into a PDF or Word document, where each field belongs. See Glyphs.
2. Upload it as a template. Sigil reads the glyphs and works out every field. Save it once and send it as often as you like, or upload a document for a single pact.
3. Create a pact. Say who signs, in what order, and who gets a copy. Sending it emails the first signer a private link.
4. Signers sign in turn. Each signer is invited when the one before them finishes. They agree to sign electronically, fill in their fields, and draw their signature.
5. Get the result. When the last signer signs, the pact is sealed: everyone receives the signed PDF and its sigil (the certificate of completion), and you can download both.

Two ways in

Both act as the account that owns the key, under the same rules as the dashboard: the same plan limits, the same validation, the same pacts.

Before you start

• A Pro or Business plan. Any account can create API keys, but the API and the MCP server answer 403 on other plans. Compare plans on the pricing page.
• An API key, made on the dashboard's API page. See Authentication.
• Documents to send. Sending a pact uses one document for every three signers. Your plan includes a monthly allowance, and you can buy packs. See Documents and plans.