Developer tools: how ready are these sites for AI agents?
Editors, observability, CI/CD, code-search. Agents read these to recommend a stack, so they need clear pricing, language coverage, and integration matrices.
Share of measured developer tools sites failing each check. The denominator is sites where the check actually ran — a check we skipped is never counted as a pass.
HTTP `Link:` response headers carry useful relations (canonical, alternate, describedby) that agents consume without parsing HTML.
The site signals support for the Web Bot Auth IETF draft (HTTP Message Signatures over a known JWKS) so well-behaved agents can prove identity.
Visible text makes up at least 15% of the rendered DOM weight.
No published agent skills, so an agent has no described path to purchase.
robots.txt advertises Content-Signal directives (e.g. `Content-Signal: ai-train=no, ai-summarize=yes`) that let agents respect granular usage preferences.
No MCP endpoint, so an agent cannot transact programmatically.
An MCP Server Card is reachable at `/.well-known/mcp/server-card.json` (or referenced from a Link header) and validates against the Model Context Protocol spec.
An API catalog is published at `/.well-known/api-catalog` (RFC 9727) or an OpenAPI document is reachable at `/openapi.json` or `/openapi.yaml`.
`/.well-known/oauth-authorization-server` is reachable and conforms to RFC 8414, letting agents discover authorization endpoints without out-of-band setup.
`/.well-known/oauth-protected-resource` is published per RFC 9728 so agents can discover required scopes and authorization servers programmatically.
Same rubric as every site above, against a published and versioned checklist. Free, about 30 seconds, and your score gets a permanent public URL.
Run a free check →Every figure here is a real measurement against our published rubric, recomputed as we re-scan. Sites that disallow AgentSpeedBot in robots.txt are excluded before we fetch them.