# Docusign: 21 point Door Gap
- Site: docusign.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: unknown
- Report: https://www.seconddoor.io/r/docusign-vrjq74
- Scanner version: 12
A document signing platform with open machine access but no machine-readable API specification or integration hooks.
## Scores
| Measure | Score |
| --- | --- |
| Humans | 69/100 |
| Agents | 48/100 |
| Composite | 59/100 |
| Door Gap | 21 points |
The human score is the mean of the four human dimensions, the agent score the mean of the six agent dimensions, and the Door Gap the difference between them.
## What the machine actually did
The agent got through 7 of 13 requests, but could not read the site's own guide for language models. It came up empty on 5 other checks too. That is enough missing for a machine to give up before it reaches a purchase.
- ok      reach the site at all
- ok      find out whether machines are welcome
- ok      ask whether the door opens for requests carrying the AI crawlers' names
- missing read the site's own guide for language models
- ok      find out what pages exist
- missing find a contact route for machines
- missing find a published agent interface
- missing find an agent plugin manifest
- missing find out whether verified agents are recognised
- ok      read the homepage as data rather than as a page
- missing find a machine readable API spec
- ok      read the developer documentation
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **No security.txt file prevents security researchers and automated systems from reporting vulnerabilities through a standard channel.** (machine_fetchable_trust)
2. **No MCP manifest or integration hooks prevent Claude, ChatGPT and other agents from acting on documents without custom plugin development.** (agent_aware_instrumentation)
3. **No llms.txt is published at the site root, so assistants get no curated map of what matters here.** (machine_discoverability)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/docusign-vrjq74
## Files generated from this scan
- **robots.txt rules for AI crawlers** at `/robots.txt`, 10 minutes, no developer needed. Verify: The next scan reads robots.txt and finds every search and agent crawler allowed, none of them kept off product or pricing paths.
- **Machine interfaces: where you stand** at `notes`, 10 minutes, no developer needed. Verify: The next scan finds the interface you published answering at its well-known path, and that check passes.
- **security.txt** at `/.well-known/security.txt`, 10 minutes, no developer needed. Verify: The next scan fetches /.well-known/security.txt as text and the security.txt check passes.
- **llms.txt** at `/llms.txt`, 15 minutes, no developer needed. Verify: The next scan fetches /llms.txt as text and the llms.txt check passes.
Each file is written from what this scan found on the site. The content is in the JSON once the evidence is opened: https://www.seconddoor.io/api/reports/docusign-vrjq74
## The agent door
- **machine_discoverability** 86/100. No AI crawler is blocked by robots.txt; the site explicitly allows gptbot, claudebot, perplexitybot and others. A real browser is served the page normally. The sitemap lists 1656 URLs across multiple child sitemaps.
- **programmatic_onboarding** null/100. Not scored: a blog is not measured on this.
- **pricing_legibility** null/100. Not scored: a blog is not measured on this.
- **agent_aware_instrumentation** 18/100. No MCP manifest, developer documentation describes an API, but only in prose.
- **machine_fetchable_trust** 40/100. No security.txt file is published at /.well-known/security.txt. The homepage answers automated requests with HTTP 200 and serves structured data. No Web Bot Auth signals are present. Trust metadata is minimal.
- **commercial_rails** null/100. Not scored: a blog is not measured on this.
## The human door
- **steps_to_first_value** 80/100. The primary call to action is 'Try for Free', reached in 2 steps from the homepage. The signup form is 2 steps away. No payment is requested on the entry path. A visitor can reach a working signup form quickly.
- **required_fields** 90/100. The signup form contains 2 fields, and 0 of them are marked required. A visitor can submit the form with minimal data entry. Of 8 total inputs on the form, only 1 carries a validation rule, so error prevention is minimal.
- **verification_walls** 65/100. No verification requirement (email confirmation, phone verification, or CAPTCHA) appears on the signup page itself. The form accepts submission with no stated verification step visible before account creation.
- **error_recovery** 41/100. Of 8 inputs on the signup form, only 1 carries a validation rule (a constraint attribute). No inline error containers are present. Live regions total 6, suggesting some error messaging infrastructure exists.
---
Scored by SecondDoor. Method: https://www.seconddoor.io/methodology
Scan another site: https://www.seconddoor.io
Rate an issue or this report: POST https://www.seconddoor.io/api/feedback, or the rate_fix tool on https://www.seconddoor.io/api/mcp