Let Agents In

Agent readiness · Documents and e-signature

dropboxsign.com

6 of 13 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

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • FAIL
    llms.txt publishedNo llms.txt at any of the 4 locations probed
  • PASS
    Docs readable without JavaScript4,633 characters of text without JS
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
  • FAIL
    MCP surfaceNo MCP surface: nothing answered at mcp.dropboxsign.com, mcp.dropboxsign.com/mcp, mcp.dropboxsign.com/v1/mcp, api.dropboxsign.com/mcp, /mcp or /api/mcp, and no file mentions MCP

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.hellosign.com/account/signUp is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
  • FAIL
    Signup reachable without a browserhttps://app.hellosign.com/account/signUp is reachable, but its form needs JavaScript

D · Provisioning

  • UNMEASURED
    Programmatic 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.
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://www.dropboxsign.com/products/dropbox-sign/pricing: "free plan", "Free trial"

E · Integration

  • PASS
    Typed SDK on the registry@dropbox/sign@1.11.0 ships types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.dropboxsign.com/developers, 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 dropboxsign.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.

Scan a domain yourself