Agent readiness · betterstack.com
2026-08-12 10:31 UTC · formula v9.2 · 2.2s
A recaptcha challenge sits between an agent and an account it was ready to create.
https://betterstack.com/users/sign-up loads recaptcha. There is no version of that an agent solves.
- A · Discovery
- 4/5
- B · Agent entry
- 2/4
- C · Registration
- 1/2
- D · Provisioning
- 1/3
- E · Integration
- 1/1
of the 15 points that apply to you and we could measure · 2 of 17 were not scored
You 9 · category median 8 · best honeybadger.io 11 · 15 deterministic HTTP checks, published formula
Fix this first
This is the whole list: everything we could measure and you do not pass. Another 2 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.
- 1llms.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.
- 2Agent entry pointan afternoon · +2
Publish /agent-signup.md: the path from nothing to a working key, written as steps for a machine rather than a tour for a person. Ours is at /agent-signup.md if you want a worked example, and it says plainly that we have nothing to sign up for.
- 3Programmatic key provisioningan afternoon · +2
Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.
Cheap too, same week
- No CAPTCHA in the signup HTML an afternoon · +1Trigger recaptcha on a risk signal instead of on every signup, or open an API path to an account. A CAPTCHA is a hard stop, not a speed bump.
Take it with you
5 of the checks an agent depends on, betterstack.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 betterstack.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.
Against error monitoring
You are 3 of 7 in a category where a developer is trying to find out an exception happened before a customer tells you.
- 1honeybadger.io11/16
- 2sentry.io10/15
- 3betterstack.comyou9/15
- 4rollbar.com8/14
- 5bugsnag.com7/15
- 6raygun.com7/16
- 7highlight.io6/15
Where competitors pass and betterstack.com does not
- llms.txt publishedsentry.io · rollbar.com · honeybadger.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
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
- 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 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.
- PASSDocs 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/
- 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
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shellA markdown file written for a machine turns a guessing game into a procedure it can follow.
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://betterstack.com/mcp, answered 401 with an auth challenge
C · Registration
- FAILNo CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTMLA CAPTCHA is a hard stop. Permissions after signup beat a gate before it.
- PASSSignup reachable without a browserForm renders in server HTML at https://betterstack.com/users/sign-up
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 4 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://betterstack.com/pricing: "$0"
E · Integration
- UNMEASUREDTyped 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.
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://betterstack.com/docs/getting-started/welcome.md
What we discovered on the way
- Docs
- https://betterstack.com/docs/getting-started/welcome/ · linked from the site
- Pricing
- https://betterstack.com/pricing · linked from the site
- Signup
- https://betterstack.com/users/sign-up · linked from the site
- npm package
- not found
- GitHub
- not found
- Package licence
- not found
- Crawl-delay
- none
- Content-Signal
- search=yes, ai-input=yes, ai-train=yes
- Blocked on-demand agents
- none