Let Agents In

Agent readiness · docuseal.com

2026-08-12 10:19 UTC · formula v9.2 · 2.2s

There is no door built for a machine anywhere on your domain.

None of the nine known agent entry paths answered, including /agent-signup.md and /.well-known/agent-access.json.

9/ 12
A · Discovery
4/5
B · Agent entry
1/2
C · Registration
2/2
D · Provisioning
1/1
E · Integration
1/2

of the 12 points that apply to you and we could measure · 5 of 17 were not scored

You 9 · category median 7.5 · best docuseal.com 9 · 15 deterministic HTTP checks, published formula

Pass it onEmail itLinkedIn

Fix this first

+2points, taking 9/12 to 11/12, past useanvil.com

This is the whole list: everything we could measure and you do not pass. Another 5 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

  1. 1
    llms.txt publishedminutes · +1

    Publish /llms.txt: a markdown list linking your quickstart, API reference, pricing and package name. It is the cheapest file on this list.

  2. 2
    Machine-readable API descriptionan afternoon · +1

    Publish an OpenAPI file at /openapi.json, or serve markdown when a client sends Accept: text/markdown. Either one stops agents guessing your API.

Then, when you have room

  • OAuth dynamic client registration a project · +1Your OAuth metadata is already published and has no registration_endpoint in it. Adding that one field is the whole change: RFC 7591 is the only standard way an agent registers itself without a human.

Take it with you

4 of the checks an agent depends on, docuseal.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on docuseal.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in fullWhat the same run on docuseal.com costs

Against documents and e-signature

You lead the 6 we have scanned in this category.

  1. 1
    docuseal.comyou
    9/12
  2. 2
    useanvil.com
    10/15
  3. 3
    documenso.com
    9/16
  4. 4
    pandadoc.com
    5/9
  5. 5
    dropboxsign.com
    6/13
  6. 6
    pdfmonkey.io
    6/13

Where competitors pass and docuseal.com does not

  • llms.txt publisheddocumenso.com · pandadoc.com · useanvil.com
  • OAuth dynamic client registrationpandadoc.com · useanvil.com
  • Machine-readable API descriptionuseanvil.com · pdfmonkey.io

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

A
DiscoveryCan an agent find and read you?
4/5
B
Agent entryIs there a door built for a machine?
1/2
C
RegistrationCan an agent get an account?
2/2
D
ProvisioningCan it get credentials without a human?
1/1
E
IntegrationCan it ship working code?
1/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

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 probedA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
  • PASS
    Docs readable without JavaScript12,455 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

  • UNMEASURED
    Agent 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.
  • FAIL
    OAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in itRFC 7591 is the only standard path by which an agent can register itself without a human.
  • PASS
    MCP surfaceLive MCP endpoint at https://www.docuseal.com/mcp, answers JSON

C · Registration

  • PASS
    No CAPTCHA in the signup HTMLNo CAPTCHA vendor in the server HTML. A widget mounted later by JavaScript would not show here.
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://docuseal.com/sign_up

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.docuseal.com/pricing: "Free Account", "$0", "Open source Free"

E · Integration

  • PASS
    Typed SDK on the registry@docuseal/api@1.0.24 ships types
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://www.docuseal.com/docs/api, and no markdown negotiationAn OpenAPI file or markdown negotiation lets an agent read your API instead of guessing it.Point at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

What we discovered on the way

Docs
https://www.docuseal.com/docs/api · linked from the site
Pricing
https://www.docuseal.com/pricing · linked from the site
Signup
https://docuseal.com/sign_up · linked from the site
npm package
@docuseal/api
GitHub
docusealco/docuseal
Package licence
MIT
Crawl-delay
none
Content-Signal
none
Blocked on-demand agents
none