Let Agents In

Agent readiness · Payments and billing

stripe.com

11 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. 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 present at https://stripe.com/llms.txt and https://docs.stripe.com/llms.txt, and the 12 links we sampled across the file all answer
  • PASS
    Docs readable without JavaScript3,912 characters of text without JS
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • PASS
    Paths robots.txt points at answerthe 2 concrete paths your robots.txt allows all answer
  • 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 2 advertised grants (authorization_code, refresh_token) finishes without a person at a browser
  • PASS
    MCP surfaceLive MCP endpoint at https://mcp.stripe.com, answered 401 with an auth challenge

C · Registration

  • FAIL
    No CAPTCHA in the signup HTMLhcaptcha appears in the signup page's server HTML, even though the form itself is assembled by JavaScript
  • FAIL
    Signup reachable without a browserhttps://dashboard.stripe.com/register is reachable, but its form needs JavaScript

D · Provisioning

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 6 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"
  • UNMEASURED
    Free tier or no-card trial stated in textUnmeasurable: https://stripe.com/pricing is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.

E · Integration

  • PASS
    Typed SDK on the registrystripe@22.5.0 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.stripe.com

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