Stripe Directory lists the route. Does an AI agent get through?

Stripe Projects can set up 31 of the 201 products we drove. At 12 of those 31, our agent still needed a person to get in through the product's own sign-up.

Stripe lists the route; our drives record whether an AI agent got through. Own profile in Stripe Directory: 26 of 201, Directory profile shows an MCP server: 0 of 26, Our drive recorded an MCP server: 26 of 26, Stripe Projects can set it up: 31 of 201, Needed a person to get in through its own sign-up: 12 of 31.

Share this card: Wide PNG · Tall PNG

Drives 1 Oct 2026 to 1 Nov 2026201 productsStep FindSubject Stripe DirectoryMarkdown

What we found.

What Stripe lists for the products we drove, and what our drives recorded
What Stripe lists, and what our drives recordedProductsShare
Own profile in Stripe Directory26 of 20113%
Directory profile shows an MCP server0 of 260%
Our drive recorded an MCP server26 of 26100%
Stripe Projects can set it up31 of 20115%
Needed a person to get in through its own sign-up12 of 3139%
Where the Directory's Machine Payments targets led
Machine Payments target opened (28 Oct 2026)TargetsShare
An llms.txt page27 of 3284%
Another page or endpoint5 of 3216%
  • Stripe Directory has its own profile for 26 of the 201 products. A profile lists the routes an agent can take: Stripe Projects, Machine Payments, an MCP server, Link or a Stripe App. It doesn't say whether an agent got through them.
  • The Directory shows an MCP server for none of those 26. Our drives recorded one for all 26.
  • At 27 of the 32 Machine Payments targets the Directory gave on 28 Oct 2026, the link opened an llms.txt page, not a payment request. Our own profile's target was one of them.

What to do.

For product owners

  • Make your own sign-up work for an agent too. An agent without the Stripe CLI never sees your Stripe Projects listing.
  • Point your Machine Payments action at an endpoint that answers with a payment request, not at a page of docs.
  • Add your MCP server to your Stripe profile, so an agent searching the Directory finds it.

For agent builders

  • Read a Directory profile as a list of routes to try, then check each one: a Machine Payments link may open a page of docs.
  • Before your agent signs up, look up the product's drive record to see whether an agent got in on its own.

Method and limits.

How we tested

  • Drives from 1 Oct 2026 to 1 Nov 2026, 201 products.
  • On 29 Oct 2026 we searched Stripe Directory for each product by name. A profile counts when its website is the product's own domain.
  • A product counts as set up by Stripe Projects when the Stripe Projects catalog lists it as a provider.
  • Needed a person: the product's newest drive is at L1 (Needs a person). Our agent couldn't get in on its own through any way the product itself offers.
  • On 28 Oct 2026 we opened every Machine Payments target in the profiles our searches returned, once each.

Limits

  • Our drives test each product's own ways in. Setting up a product through Stripe Projects isn't part of these counts.
  • The 32 Machine Payments targets come from every profile our searches returned, not only products we drove.
  • Counts are shown from 5 products.

See what an agent sees in yours.

Free: what an agent finds, any wall in its way and how many things to fix. The Audit ($499) gives you every fix.