Niches · Contracts, proposals & e-signatures
Send an agreement that has to meet a signing rule
Two or three companies' docs show a full fit.
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. No docs we read state these figures, so they don't count against a listing here.
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 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| BoldSign BB 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. source |
| PandaDoc B 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. source |
Does the job, with a limit 8
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.
| Listing | Why |
|---|---|
| Adobe Acrobat Sign D 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. source |
| Documenso C 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. source |
| DocuSeal B 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. source |
| Docusign B 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. source |
| Dropbox Sign B 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. source |
| airSlate SignNow B 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. source |
| SignWell B 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. source |
| Youtrust BB 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. source |
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
The same as data: /api/v1/use-cases/e-signatures.regulated-signature.json, or the MCP tool get_use_case with id e-signatures.regulated-signature. Other jobs in this category: /api/v1/niches?category=e-signatures.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.