Let Agents In

Agent readiness · Search as a service

typesense.org

9 of 16 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.

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • PASS
    llms.txt publishedllms.txt present at https://typesense.org/llms.txt and https://typesense.org/docs/llms.txt, and the 12 links we sampled across the file all answer
  • PASS
    Docs readable without JavaScript17,612 characters of text without JS, on https://typesense.org/docs/30.2/api/api-keys.html rather than on https://typesense.org/docs/
  • 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 surfaceNo MCP surface: nothing answered at mcp.typesense.org, mcp.typesense.org/mcp, mcp.typesense.org/v1/mcp, api.typesense.org/mcp, /mcp or /api/mcp, and no file mentions MCP

C · Registration

  • FAIL
    No CAPTCHA in the signup HTMLrecaptcha appears in the signup page's server HTML
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://cloud.typesense.org/signup

D · Provisioning

  • PASS
    Programmatic key provisioning2 of 7 provisioning phrases across the 6 documents we read: "management api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
  • FAIL
    Free tier or no-card trial stated in textNo free tier or no-card wording at https://cloud.typesense.org/pricing

E · Integration

  • PASS
    Typed SDK on the registrytypesense@3.0.6 ships types, matched from the registry by who publishes it rather than by a link on your site
  • FAIL
    Machine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://typesense.org/docs/, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.

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 typesense.org 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