Let Agents In

Agent readiness · Model hosting and gateways

baseten.co

9 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

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • FAIL
    llms.txt publishedllms.txt and llms-full.txt present at https://www.baseten.co/llms.txt and https://docs.baseten.co/llms.txt and https://docs.baseten.co/llms-full.txt, but 2 of the 12 links we sampled across both files are gone, starting with https://docs.baseten.co/styles/proselint/RASSyndrome.yml
  • PASS
    Docs readable without JavaScript8,205 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
  • FAIL
    OAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in it
  • PASS
    MCP surfaceLive MCP endpoint at https://api.baseten.co/mcp, answered 403 with an auth challenge

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://login.baseten.co/sign-up 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.
  • UNMEASURED
    Signup reachable without a browserUnmeasurable: https://login.baseten.co/sign-up 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

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 4 documents we read: "management api"
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://www.baseten.co/pricing/: "$0", "free credits"

E · Integration

  • PASS
    Typed SDK on the registry@basetenlabs/performance-client@0.1.12 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://docs.baseten.co/overview

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 baseten.co 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