Let Agents In

Agent readiness · Managed databases

redis.io

8 of 15 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. 1 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

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • FAIL
    llms.txt publishedllms.txt present at https://redis.io/llms.txt, but 1 of the 12 links we sampled across the file are gone, starting with https://redis.io/docs/latest/develop/interact/pubsub/index.html.md
  • PASS
    Docs readable without JavaScript6,621 characters of text without JS, on https://redis.io/docs/latest/operate/kubernetes/security/authentication/manage-rec-credentials/ rather than on https://redis.io/docs/latest/
  • PASS
    On-demand agents not blockedExplicitly allowed: ChatGPT-User
  • 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

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomains
  • PASS
    MCP surfaceLive MCP endpoint at https://redis.io/mcp, answers JSON

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://cloud.redis.io 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.
  • FAIL
    Signup reachable without a browserhttps://cloud.redis.io is reachable, but its form needs JavaScript

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 5 documents we read
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://redis.io/pricing/: "$0", "Try for free", present in one of the two fetches of that page

E · Integration

  • PASS
    Typed SDK on the registryredis@6.2.1 ships types, matched from the registry by who publishes it rather than by a link on your site
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://redis.io/docs/latest/operate/rc/api/get-started/manage-api-keys/

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 redis.io 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.

Scan a domain yourself