A recaptcha challenge sits between an agent and an account it was ready to create.

https://www.firecrawl.dev/signin loads recaptcha. There is no version of that an agent solves.

14/ 16

A · Discovery: 5/5
B · Agent entry: 4/4
C · Registration: 1/2
D · Provisioning: 2/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

Pass it onEmail it LinkedIn

Fix this first

+2points, taking 14/16 to 16/16

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.

1
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.
2
Programmatic key provisioningan afternoon · +1
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.

Take it with you

3 of the checks an agent depends on, firecrawl.dev 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 firecrawl.dev. 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.

Read the audits in full What the same run on firecrawl.dev costs

Against browser and scraping infrastructure

You are 3 of 6 in a category where a developer is trying to drive a real browser or read a page you do not own.

1
zenrows.com
13/14
2
browserbase.com
14/16
3
firecrawl.devyou
14/16
4
apify.com
12/15
5
browserless.io
12/16
6
scrapingbee.com
6/14

Where competitors pass and firecrawl.dev does not

Programmatic key provisioningbrowserbase.com · browserless.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

DiscoveryCan an agent find and read you?

5/5

Agent entryIs there a door built for a machine?

4/4

RegistrationCan an agent get an account?

1/2

ProvisioningCan it get credentials without a human?

2/3

IntegrationCan it ship working code?

2/2

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 and llms-full.txt present at https://www.firecrawl.dev/llms.txt and https://docs.firecrawl.dev/llms.txt and https://docs.firecrawl.dev/llms-full.txt, and the 12 links we sampled across both files all answer
PASS
Docs readable without JavaScript14,017 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

PASS
Agent entry pointFound: https://www.firecrawl.dev/agents.md
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.firecrawl.dev/mcp, answers JSON

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://www.firecrawl.dev/signin

D · Provisioning

PART
Programmatic key provisioning1 of 7 provisioning phrases across the 4 documents we read: "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"Documented 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://www.firecrawl.dev/pricing: "no card", "free tier", "Free Plan"

E · Integration

PASS
Typed SDK on the registryfirecrawl@4.32.0 ships types
PASS
Machine-readable API descriptionDocs serve markdown to machines, at https://docs.firecrawl.dev/introduction

What we discovered on the way

Docs: https://docs.firecrawl.dev/introduction · linked from the site
Pricing: https://www.firecrawl.dev/pricing · linked from the site
Signup: https://www.firecrawl.dev/signin · from your llms.txt
npm package: firecrawl
GitHub: firecrawl/firecrawl
Package licence: MIT
Crawl-delay: none
Content-Signal: ai-train=yes, search=yes, ai-input=yes
Blocked on-demand agents: none