Connect an agent

Connect Signit once, attach a PDF in your conversation, then ask:

Use Signit to send this attached PDF for signature to Alice (alice@example.com), Bob (bob@example.com), and Carol (carol@example.com). Use parallel signing and English invitations.

The agent transfers the original attachment, creates an Envelope, and sends it through the same workflow as the Signit interface. You do not need to upload the document separately in Signit. Provide each Signer's name and email; the agent should ask for missing addresses. If you ask only to prepare a draft, it should wait for your sending instruction.

By default Signit reads the whole PDF in the background and places each Signer's fields at their signature blocks (autoDetectSignatureFields, default true). Ask for a signature page instead and the agent passes false: no analysis, every Signer signs on an added page. While the PDF is still being read, a send request waits briefly and then reports placement pending with a retryAfterSeconds hint; nothing is sent, and the agent retries the same request.

Choose your client

• Claude.ai: attach a PDF up to 3 MiB. Code execution and network access to Signit's host are required.
• ChatGPT: add Signit in developer mode and attach a PDF up to 25 MiB. Account and workspace policy control availability.

The hosted endpoint is https://app.sign-it.ro/mcp. Sign in through OAuth; no Signit API key is needed. Existing connections must reconnect to approve creation and sending permissions.

Access and signing

A connected agent acts as your Signit User, within your existing access, in the organization you have selected. Switching organization in the app switches the agent too (see Manage your organization). You can revoke it from Agent connection. Sending requests other people's signatures; it does not sign for them. The connector also lists your pending signatures and offers authorized PDF inspection and explicit signing for your own eligible assignment. Inspection lists every field prepared for you (page and position) and a fieldSetDigest; signing must confirm that digest and applies your adopted name to every field in the set. Read the entire PDF before approving an adopted signature name and consent. Hosted review is limited to 3 MiB and requires a client that can read the private PDF resource.

Check status and void

The agent can check an Envelope you sent with signit_get_envelope_status: each Signer's progress, who it is still waiting for, and when it was sent, completed or voided. It sees only your own Envelopes.

If you ask it to cancel an Envelope, the agent voids it with signit_void_envelope. Signers who have not signed are emailed that it was cancelled, and nobody can sign it after that. Signed copies are kept. A reason is optional, up to 500 characters, and Signers see it in that email. Voiding an Envelope that is already voided changes nothing. There is no reminder tool: send reminders from the Envelope page in Signit.

Text and checkbox fields

When you ask for them, the agent can add Text and Checkbox Fields while creating an Envelope. Each one names its Signer by email, a key, a label, the page and the position. Signit checks them with the same rules as the editor; the agent should not invent fields, labels or prefilled text you did not ask for. A draft with these fields is sent only with the expectedDefinitionRevision the creation returned. If Signit then places the signature fields, sending returns the concrete fields, positions, Signers and Original digest with the new revision. The agent must show those placements to you and confirm that field set before retrying Send.

An Envelope with Text or Checkbox Fields (signingFormatVersion 2) is signed in three steps, even if your own part has only signatures:

1. Inspect lists the fields, your saved answers, other Signers' submitted answers and, in completion.answerFieldIds, exactly which fields you answer.
2. Review (signit_review_signature) sends your answers and adopted name to Signit, which returns everything that will appear on the document. The agent must show you those values and get your consent.
3. Sign sends the same answers with the review token. Changed answers need a new review; the review expires after an hour.

The agent passes only answers you stated: null means "not provided" for text and "left unchecked" for a checkbox. Signit records that your connected agent submitted them. A signature-only call to such an Envelope is refused before anything is saved.

The new chat-attachment flows still require live verification in Claude.ai and ChatGPT; server tests alone do not establish account-specific client behavior.