Agent readiness · Browser and scraping infrastructure
zenrows.com
13 of 14 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
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.zenrows.com/llms.txt and https://docs.zenrows.com/llms.txt and https://docs.zenrows.com/llms-full.txt, and the 12 links we sampled across both files all answer
- PASSDocs readable without JavaScript13,046 characters of text without JS, on https://docs.zenrows.com/first-steps/getting-started-guide rather than on https://docs.zenrows.com/first-steps/welcome
- PASSOn-demand agents not blockedExplicitly allowed: ChatGPT-User
- 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.zenrows.com/skill.md
- PASSOAuth dynamic client registrationregistration_endpoint published, but none of the 1 advertised grants (authorization_code) finishes without a person at a browser
- PASSMCP surfaceLive MCP endpoint at https://mcp.zenrows.com/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.zenrows.com/register 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.
- UNMEASUREDSignup reachable without a browserUnmeasurable: https://app.zenrows.com/register answers 403 to an agent and 403 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.
D · Provisioning
- PARTProgrammatic key provisioning1 of 7 provisioning phrases across the 5 documents we read: "service account"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://zenrows.com/pricing: "no card"
E · Integration
- PASSTyped SDK on the registryzenrows@2.0.2 ships types
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://docs.zenrows.com/first-steps/welcome
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for zenrows.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.