Let Agents In

Agent readiness · sentry.io

2026-08-12 10:07 UTC · formula v9.2 · 20.7s

Only 1,863 characters of your documentation survive without JavaScript, and that is the version an agent reads.

https://docs.sentry.io/platforms/apple/data-management/ served 1,863 characters of text to a plain fetch. The check passes at 2,000, which is about one screen of prose.

10/ 15
A · Discovery
4/5
B · Agent entry
3/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 10 · category median 8 · best honeybadger.io 11 · 15 deterministic HTTP checks, published formula

Pass it onEmail itLinkedIn

Fix this first

+4points, taking 10/15 to 14/15, past honeybadger.io

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.

  1. 1
    Programmatic 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.

  2. 2
    Agent entry pointan afternoon · +1

    The file is there and it states a policy rather than a procedure. It counts when it names a credential, an endpoint or a way to get an account: the path from nothing to a working key, in steps. Ours is at /agent-signup.md and it is 1.7 kB.

  3. 3
    No CAPTCHA in the signup HTMLan afternoon · +1

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

Then, when you have room

  • Docs readable without JavaScript a project · +1Server-render the docs or mirror them as markdown. A plain fetch gets 1,863 characters, just under the 2,000 we look for.

Take it with you

5 of the checks an agent depends on, sentry.io 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 sentry.io. 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 2 of 7 in a category where a developer is trying to find out an exception happened before a customer tells you.

  1. 1
    honeybadger.io
    11/16
  2. 2
    sentry.ioyou
    10/15
  3. 3
    betterstack.com
    9/15
  4. 4
    rollbar.com
    8/14
  5. 5
    bugsnag.com
    7/15
  6. 6
    raygun.com
    7/16
  7. 7
    highlight.io
    6/15

Where competitors pass and sentry.io does not

  • Docs readable without JavaScriptrollbar.com · bugsnag.com · honeybadger.io · betterstack.com · highlight.io · raygun.com

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?
3/4
C
RegistrationCan an agent get an account?
1/2
D
ProvisioningCan it get credentials without a human?
1/3
E
IntegrationCan it ship working code?
1/1

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)
  • PASS
    llms.txt publishedllms.txt present at https://sentry.io/llms.txt and https://docs.sentry.io/llms.txt, and the 12 links we sampled across the file all answer
  • FAIL
    Docs readable without JavaScriptOnly 1,863 characters render without JS, on https://docs.sentry.io/platforms/apple/data-management/ rather than on https://docs.sentry.io/Most agents fetch HTML, they do not run your bundle. An empty shell reads as an empty product.
  • 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

  • PART
    Agent entry pointOnly service descriptors: https://sentry.io/.well-known/mcp.json. No procedure written for a machine.A markdown file written for a machine turns a guessing game into a procedure it can follow.
  • 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://mcp.sentry.dev/mcp, answered 401 with an auth challenge

C · Registration

  • FAIL
    No 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.
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://sentry.io/signup/

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://sentry.io/pricing/: "$0", "Free Developer Plan"

E · Integration

  • PASS
    Typed SDK on the registry@sentry/browser@10.70.0 ships types
  • UNMEASURED
    Machine-readable API descriptionUnmeasurable: the site answers unknown markdown paths with text, so the markdown it served is not evidence of negotiation

What we discovered on the way

Docs
https://docs.sentry.io/ · linked from the site
Pricing
https://sentry.io/pricing/ · linked from the site
Signup
https://sentry.io/signup/ · linked from the site
npm package
@sentry/browser
GitHub
getsentry/sentry-python
Package licence
MIT
Crawl-delay
none
Content-Signal
search=yes, ai-input=yes, ai-train=yes
Blocked on-demand agents
none