Agent readiness · browserbase.com
2026-08-12 10:37 UTC · formula v9.2 · 6.8s
A recaptcha challenge sits between an agent and an account it was ready to create.
https://www.browserbase.com/sign-up loads recaptcha. There is no version of that an agent solves.
- A · Discovery
- 5/5
- B · Agent entry
- 3/4
- C · Registration
- 1/2
- D · Provisioning
- 3/3
- E · Integration
- 2/2
of the 16 points that apply to you and we could measure · 1 of 17 were not scored
You 14 · category median 12.5 · best zenrows.com 13 · 15 deterministic HTTP checks, published formula
Fix this first
This is the whole list: everything we could measure and you do not pass. Another 1 point sits behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.
- 1No 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
- OAuth dynamic client registration a project · +1Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.
Take it with you
3 of the checks an agent depends on, browserbase.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 browserbase.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 browser and scraping infrastructure
You are 2 of 6 in a category where a developer is trying to drive a real browser or read a page you do not own.
- 1zenrows.com13/14
- 2browserbase.comyou14/16
- 3firecrawl.dev14/16
- 4apify.com12/15
- 5browserless.io12/16
- 6scrapingbee.com6/14
Where competitors pass and browserbase.com does not
- OAuth dynamic client registrationapify.com · firecrawl.dev · browserless.io · zenrows.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
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)
- PASSllms.txt publishedllms.txt and llms-full.txt present at https://www.browserbase.com/llms.txt and https://docs.browserbase.com/llms.txt and https://docs.browserbase.com/llms-full.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript6,360 characters of text without JS, on https://docs.browserbase.com/welcome/quickstarts/agents rather than on https://docs.browserbase.com/welcome/introduction
- 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
- PASSAgent entry pointFound: https://www.browserbase.com/skill.md
- FAILOAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
- PASSMCP surfaceLive MCP endpoint at https://mcp.browserbase.com/mcp, answers JSON
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://www.browserbase.com/sign-up
D · Provisioning
- PASSProgrammatic key provisioning3 of 7 provisioning phrases across the 7 documents we read: "management api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic", "service account"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://www.browserbase.com/pricing: "Free Plan", "$0", "Try for free"
E · Integration
- PASSTyped SDK on the registry@browserbasehq/sdk@2.16.0 ships types
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://docs.browserbase.com/welcome/introduction
What we discovered on the way
- Docs
- https://docs.browserbase.com/welcome/introduction · linked from the site
- Pricing
- https://www.browserbase.com/pricing · linked from the site
- Signup
- https://www.browserbase.com/sign-up · linked from the site
- npm package
- @browserbasehq/sdk
- GitHub
- not found
- Package licence
- Apache-2.0
- Crawl-delay
- none
- Content-Signal
- none
- Blocked on-demand agents
- none