# Send an agreement that has to meet a signing rule

> Send an agreement that has to meet a signing rule: 2 companies fully do it, 8 with a limit, 10 carry the tag. Every listing in Contracts, proposals & e-signatures with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/e-signatures.regulated-signature/
- Markdown: https://www.anchorterminal.com/niches/e-signatures.regulated-signature/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/e-signatures.regulated-signature/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/e-signatures.regulated-signature/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 10 | 13 | 2 |

## What counts as done

A request sent with the required level or control set by a documented parameter, and the audit trail recording that control.

Measured, for our own tests: in the same number of calls as an ordinary send.

How agents ask for it: this needs a qualified signature; the signer must read the whole form first; use an eIDAS advanced signature; send it with ID verification

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **BoldSign (Syncfusion, Inc.)**: The send call itself takes AuthenticationType (email, SMS OTP, access code), IdentityVerificationSettings and EnableQes for one signer, so the control is a documented parameter on an ordinary send; identity verification has its own report endpoint.
- **PandaDoc (PandaDoc)**: verification_settings on a recipient at document creation require a passcode, SMS one-time password, KBA or ID check before open, in the same create call as an ordinary send.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Adobe Acrobat Sign (Adobe Inc.)**: Participant securityOption takes an authenticationMethod such as PASSWORD or PHONE on the create call. The guide lists signatureType ESIGN or WRITTEN only; no digital, cloud or qualified signature parameter was found in the readable pages.
- **Documenso (Documenso, Inc.)**: Recipients take actionAuth and accessAuth of ACCOUNT, PASSKEY, TWO_FACTOR_AUTH or PASSWORD on the create call. No eIDAS AES or QES level, SMS or ID check parameter exists in the spec.
- **DocuSeal (DocuSeal, LLC)**: require_phone_2fa and require_email_2fa are submitter parameters on the ordinary send. EU QES, ID card verification and KBA are priced on Pro, but no parameter for them appears in the create-submission reference.
- **Docusign (Docusign, Inc.)**: Signers take identityVerification by workflow id and recipientSignatureProviders for standards-based digital signatures on the ordinary create call. Which providers give eIDAS AES or QES sits on a Developer Center page that renders by script.
- **Dropbox Sign (Dropbox, Inc.)**: Signers take pin and sms_phone_number, and is_eid turns on eID verification on the send call. eID needs a sales add-on, works for one signer only and not in test mode; QES is described in the glossary without a send parameter found.
- **airSlate SignNow (airSlate, Inc.)**: Invites take authentication_type password, phone or sms per signer and the history records authentication failures. id_verification_required appears only as a read field, and no eIDAS AES or QES parameter was found.
- **SignWell (Docsketch, LLC (DBA SignWell))**: Recipients can be sent a passcode by SMS and Update Authentication changes it after sending; a NOM-151 certificate endpoint serves Mexico. No eIDAS AES or QES level or ID check parameter exists.
- **Youtrust (Youtrust SAS)**: Each signer takes signature_level (electronic, advanced, qualified) and signature_authentication_mode (otp_email, otp_sms) on the ordinary flow, and identity documents can be pre-verified. AES and QES are paid add-ons on top of the API plan.

## What stops agents finishing

- required signature level not on the plan or not in the API
- control exists in the web app only

## Around it

Before: identity-verification.verify-person. After: e-signatures.fetch-signed-file.

## Where this comes from

Weight 13 of 100 in Contracts, proposals & e-signatures: 2 of 31 accounts (Illinois Shines read-through rule, a PowerForm needing extra signers) plus the eIDAS AES and QES work Documenso and Youtrust describe; weight raised by hand above the count because a missing control stops the job outright

As data: https://www.anchorterminal.com/api/v1/use-cases/e-signatures.regulated-signature.json, or the MCP tool get_use_case with id e-signatures.regulated-signature. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
