Let Agents In

Agent readiness · Background jobs and workflows

upstash.com

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)
  • PASS
    llms.txt publishedllms.txt and llms-full.txt present at https://upstash.com/llms.txt and https://upstash.com/llms-full.txt and https://docs.upstash.com/llms.txt, and the 12 links we sampled across both files all answer
  • PASS
    Docs readable without JavaScript2,803 characters of text without JS, on https://upstash.com/docs/redis/features/credential-protection rather than on https://upstash.com/docs/introduction
  • 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

  • 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
  • FAIL
    MCP surfaceMCP mentioned 6x in your own files, but nothing answered at mcp.upstash.com, mcp.upstash.com/mcp, mcp.upstash.com/v1/mcp, api.upstash.com/mcp, /mcp or /api/mcp

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://console.upstash.com 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://console.upstash.com is reachable, but its form needs JavaScript

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 7 documents we read
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://upstash.com/pricing: "free tier", "$0", "Free Free Pay as you go"

E · Integration

  • PASS
    Typed SDK on the registry@upstash/redis@1.38.2 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://upstash.com/docs/introduction

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 upstash.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.

Scan a domain yourself