Let Agents In

Agent readiness · Error monitoring

betterstack.com

9 of 15 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. 1 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 JavaScript10,551 characters of text without JS, on https://betterstack.com/docs/getting-started/team-and-account-management/reporting/ rather than on https://betterstack.com/docs/getting-started/welcome/
  • 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
  • PASS
    OAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
  • PASS
    MCP surfaceLive MCP endpoint at https://betterstack.com/mcp, answered 401 with an auth challenge

C · Registration

  • FAIL
    No CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://betterstack.com/users/sign-up

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 4 documents we read
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://betterstack.com/pricing: "$0"

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://betterstack.com/docs/getting-started/welcome.md

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 betterstack.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