State of agent readiness
Can an agent use a developer tool? Measured every week.
Developer-tool companies checked with Beacon every week, one seventh of the list each night, so the readiness of the sector can be followed over time. Chosen on 2026-10-01 as products that sell to developers or to agents; not a random sample. Each site gets the same Beacon check: whether an agent can find it, read it and use it. Below: the last seven days against the seven before.
What the sites publish
| Measure | This week | Last week | Change |
|---|---|---|---|
| Publishes llms.txt | 88% (61 of 69) | – | |
| Serves markdown on request | 51% (35 of 69) | – | |
| OpenAPI at a standard address | 17% (12 of 69) | – | |
| Publishes an MCP server card | 29% (20 of 69) | – | |
| A hosted MCP endpoint answers | 29% (20 of 69) | – | |
| Publishes an A2A agent card | 3% (2 of 69) | – | |
| Serves its home page to a bot | 99% (68 of 69) | – | |
| robots.txt lets AI agents in | 88% (61 of 69) | – |
By segment
Each site
The aggregates above are public. The score of each named site is shown to signed-in users, so a company’s result is read by someone, not indexed. Create a free account or sign in.
The panel is a chosen list, not a sample of the industry: 69 products that sell to developers or to agents, picked on 1 October 2026. A seventh of the list is checked each night, so “this week” is every site’s latest check in the last seven days. Checks are read-only, about twenty requests per site, identified as OverwingBeacon.