Niches · Contracts, proposals & e-signatures
Turn an agent-drafted agreement into a signable document
One company's docs show a full fit.
What counts as done
A document where each signature, date and text field sits at its intended place (by tag, anchor text or coordinates) on the right page, sent to the signers, with no placeholder left unresolved.
Measured, for our own tests: in at most three calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: I drafted this contract, send it for signing
, make this markdown into a PDF and get it signed
, put signature and date fields on this document
, generate the contract from these terms
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| airSlate SignNow B airSlate, Inc. | Upload document with tags accepts .doc, .docx and .pdf with positional text tags carrying type, role, label and prefilled text, then one invite call sends it: two calls. HTML is supported only through the NetSuite integration. source |
Does the job, with a limit 9
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. | Upload to /transientDocuments, then POST /agreements with formFieldGenerators placing fields by anchorText with offsets, or text tags: two calls. The usage guide shows PDF uploads only, so a Markdown or HTML draft must be rendered first. source |
| BoldSign BB Syncfusion, Inc. | Send accepts PDF, DOCX, XLSX, PPTX and images with UseTextTags=true and {{sign|1|*}} tags, or bounds in points. No HTML or Markdown source, so an agent's draft must become a file first; the troubleshooting page lists fields in the wrong place and tags not becoming fields. source |
| Documenso C Documenso, Inc. | POST /envelope/create takes a PDF, field/create-many places fields by page and percentage coordinates or by a text placeholder with matchAll, then /envelope/distribute sends: three calls. PDF only, so a Markdown or HTML draft must be rendered elsewhere first. source |
| DocuSeal B DocuSeal, LLC | POST /submissions/html, /pdf and /docx send a one-off document in one call, with {{Field;role=...;type=...}} text tags or pixel coordinates. acc-08 and acc-09 report HTML-tag fields landing stacked or on the wrong page; both closed in June 2026 with no fix in the thread. source |
| Docusign B Docusign, Inc. | Documents accept non-PDF files with fileExtension (converted to PDF) or an htmlDefinition, and tabs anchor to anchorString with offsets, sent in one create call. acc-27's sign tab did not appear over its anchor, and acc-06's agent flow fell back to a person uploading. source |
| Dropbox Sign B Dropbox, Inc. | POST /signature_request/send takes files or file_urls with use_text_tags or form_fields_per_document coordinates, one call. The spec names no HTML or Markdown input, so an agent's draft must become a file first. source |
| PandaDoc B PandaDoc | Upload a PDF, DOCX or RTF with field tags like {signature*:role:id___} that bind to recipient roles, wait for draft, then send. No HTML or Markdown source, and the asynchronous wait adds a status call. source |
| SignWell B Docsketch, LLC (DBA SignWell) | POST /api/v1/documents accepts .html, .docx, .pdf and more by URL or base64, with text_tags or fields by coordinates, in one call. acc-16 had recipient names dropped on DOCX text-tag sends through the MCP, fixed in September 2026. source |
| Youtrust BB Youtrust SAS | Documents accept PDF or DOCX with parse_anchors for Smart Anchors (signature, date, text, checkbox and more), but the flow is create request, add document, add signers, activate: four calls, over the three in the success criterion. No HTML or Markdown source. source |
What stops agents finishing
- fields from HTML or tags land in the wrong place with no error
- generated placeholders sent unresolved
- the agent has to hand a file to a person to upload
Around it
Before: llm.draft-contract, document-extraction.read-pdf. After: e-signatures.track-status.
Where this comes from
Weight 19 of 100 in Contracts, proposals & e-signatures: 6 of 31 accounts: two DocuSeal HTML-template field position bugs, Docusign DocGen placeholders and anchor tabs, Adobe date fields, and the Signbee author's account of agents stopping at the upload step
The same as data: /api/v1/use-cases/e-signatures.generate-and-send.json, or the MCP tool get_use_case with id e-signatures.generate-and-send. 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.