Let Agents In

Agent readiness · Domain registration and DNS

opensrs.com

5 of 12 measurable points under formula 9.57, measured on 2026-09-03. 16 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 4 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/bot)
  • FAIL
    Price or entry condition in the search snippetYour pricing page's description tag names no amount and no entry condition: “Get competitive, flexible, tiered pricing on 730+ TLDs. Save more as you grow with transparent domain costs and no monthly fees.”Put the number, or the entry condition in words ("free tier", "no credit card"), into the pricing page's meta description. That string is what an agent reads when it decides whether to open you at all.
  • FAIL
    llms.txt publishedNo llms.txt at any of the 4 locations probed: https://opensrs.com/llms.txt, https://opensrs.com/llms-full.txt, https://docs.opensrs.com/llms.txt, https://opensrs.com/resources/documentation/llms.txt
  • PASS
    Docs readable without JavaScript4,029 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 13 agent entry paths we asked on your site returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 12 hosts probed: https://opensrs.com, https://auth.opensrs.com, https://login.opensrs.com, https://accounts.opensrs.com, and 8 more
  • FAIL
    MCP surfaceNo MCP surface: nothing spoke MCP at mcp.opensrs.com, mcp.opensrs.com/mcp, mcp.opensrs.com/v1/mcp, api.opensrs.com/mcp, api.opensrs.com/v1/mcp, /mcp or /api/mcp, and any address you publish in the MCP registry, and no file mentions MCP

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://opensrs.com/join 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://opensrs.com/join 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.
  • UNMEASURED
    Free tier or no-card trial stated in textUnmeasurable: https://opensrs.com/pricing is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.

E · Integration

  • UNMEASURED
    Typed SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://opensrs.com/resources/documentation

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.

Free while we are building this, and we will ask before it ever costs anything. No card, no account, and one link in every email that stops it.

The address and the domain are the only things you give us. We keep them with what the watch needs to run: when it was created and confirmed, when it was last checked, and the score it was last compared against. Who holds it and how to have it deleted.

This page is the newest scan we hold for opensrs.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.

If a line here is wrong, rescan it first, because most of what we get told is already fixed and the page is only as new as the last scan. If it is still wrong after that, write to hello@letagentsin.com with the check and what you see instead. A verdict we cannot reproduce comes down, and the rule that produced it gets fixed for everybody rather than only for you.

Scan a domain yourself