Agent readiness · Documents and e-signature
docuseal.com
9 of 12 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- FAILllms.txt publishedNo llms.txt at any of the 4 locations probed
- PASSDocs readable without JavaScript12,455 characters of text without JS
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- UNMEASUREDAgent entry pointUnmeasurable: 1 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
- FAILOAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in it
- PASSMCP surfaceLive MCP endpoint at https://www.docuseal.com/mcp, answers JSON
C · Registration
- PASSNo CAPTCHA in the signup HTMLNo CAPTCHA vendor in the server HTML. A widget mounted later by JavaScript would not show here.
- PASSSignup reachable without a browserForm renders in server HTML at https://docuseal.com/sign_up
D · Provisioning
- UNMEASUREDProgrammatic key provisioningUnmeasurable: only 1 documentation page could be read, which is too little to conclude anythingLink your API reference from your docs index or from llms.txt and this becomes measurable.
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.docuseal.com/pricing: "Free Account", "$0", "Open source Free"
E · Integration
- PASSTyped SDK on the registry@docuseal/api@1.0.24 ships types
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.docuseal.com/docs/api, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for docuseal.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.