Let Agents In

Agent readiness · Managed databases

turso.tech

11 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://turso.tech/llms.txt and https://turso.tech/llms-full.txt and https://docs.turso.tech/llms.txt and https://docs.turso.tech/llms-full.txt, and the 12 links we sampled across both files all answer
  • PASS
    Docs readable without JavaScript2,889 characters of text without JS
  • 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
  • PASS
    OAuth dynamic client registrationregistration_endpoint published, but none of the 1 advertised grants (authorization_code) finishes without a person at a browser
  • PASS
    MCP surfaceLive MCP endpoint at https://api.turso.tech/mcp, answered 401 with an auth challenge

C · Registration

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

D · Provisioning

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 5 documents we read: "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic"
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://turso.tech/pricing: "no credit card", "$0", "Developer Scaler Yes Pro Yes SSO Free"

E · Integration

  • PASS
    Typed SDK on the registry@tursodatabase/database@0.7.2 ships types
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://docs.turso.tech/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 turso.tech 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

Is turso.tech ready for AI agents? 11/15 · Let Agents In