Agent readiness · apify.com
2026-08-12 10:37 UTC · formula v9.2 · 3.9s
Nowhere in your documentation does an agent learn how to get a key without a human.
No management API, service account or programmatic key creation is described in the pages we read.
- A · Discovery
- 5/5
- B · Agent entry
- 4/4
- C · Registration
- 0/1
- D · Provisioning
- 1/3
- E · Integration
- 2/2
of the 15 points that apply to you and we could measure · 2 of 17 were not scored
You 12 · 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 2 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.
- 1Programmatic 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.
Then, when you have room
- Signup reachable without a browser a project · +1Let https://console.apify.com/sign-up render its form in server HTML and stop refusing non-browser requests to it.
Take it with you
3 of the checks an agent depends on, apify.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 apify.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 4 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.com14/16
- 3firecrawl.dev14/16
- 4apify.comyou12/15
- 5browserless.io12/16
- 6scrapingbee.com6/14
Where competitors pass and apify.com does not
- Signup reachable without a browserbrowserbase.com · firecrawl.dev
- 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
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://apify.com/llms.txt and https://docs.apify.com/llms.txt and https://docs.apify.com/llms-full.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript6,824 characters of text without JS, on https://docs.apify.com/academy/api-scraping/general-api-scraping/cookies-headers-tokens rather than on https://docs.apify.com/
- 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://apify.com/agents.md
- 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://mcp.apify.com, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://console.apify.com/sign-up is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://console.apify.com/sign-up is reachable, but its form needs JavaScriptIf a bare HTTP request gets a 403, the agent never sees the form at all.
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 7 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://apify.com/pricing: "No credit card", "free plan", "$0"
E · Integration
- PASSTyped SDK on the registryapify@3.7.2 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionOpenAPI at https://apify.com/openapi.json
What we discovered on the way
- Docs
- https://docs.apify.com/ · linked from the site
- Pricing
- https://apify.com/pricing · linked from the site
- Signup
- https://console.apify.com/sign-up · linked from the site
- npm package
- apify (registry guess)
- GitHub
- apify/crawlee
- Package licence
- Apache-2.0
- Crawl-delay
- none
- Content-Signal
- search=yes, ai-input=yes, ai-train=yes
- Blocked on-demand agents
- none