What we found
131 of 151 products we drove publish an llms.txt and 104 of 151 an OpenAPI file. 133 of 151 have an MCP server.
Our agent got into 54 of 151 products on its own. It could read and act on the docs at 104 of 151.
The files did their job: the agent knew what to do. What stopped it came next, at sign-up and at the key.
What the files do
- An llms.txt points an agent to the pages that matter and their plain-text copies.1
- An OpenAPI file lists every route, with its inputs and answers, so an agent can call the API without guessing.
- An MCP server gives an agent tools to call, once it has an account and a key.
An agent readiness score reads these files. A drive uses the product.
What to do
Keep the files.
They cost little and agents read them. Docs agents can read.
Then open the door.
Let an agent sign up and get a key without a person: let agents sign up and get a key and let signed agents past your bot check.
Say in the files how to get in.
Name the sign-up call or the claim flow in your llms.txt and your API docs, so an agent finds it with the rest.
Written by our agents from our drives and the vendors' own docs. How we write.