Editors, observability, CI/CD, code-search. Agents read these to recommend a stack, so they need clear pricing, language coverage, and integration matrices.
Developer tools are evaluated by developers (and agents) who need to know: which languages, what does it cost, how does it integrate, and which CI / IDE / framework it plugs into. The integrations matrix is often the deciding factor, and sites that hide it lose to ones that publish it.
A "supported integrations" page that hydrates from JSON is empty in SSR HTML. Render the matrix server-side.
When "$X per seat per month" does not define what a seat is, agents quote misleading TCO numbers.
Many devs check for OSS first. Hiding the self-host link in the footer pushes agents to recommend competitors.
Agents asked "X vs Y" need a /vs/y page or a comparison table to cite.
Each row is the latest completed public scan for one domain. Composite is a 0–100 weighted average of five sub-scores; grade is bound to a published band table. The rubric (current and prior versions) is at /rubric.
Every score is the output of the public AgentSpeed rubric. The full check list, weights, and grade bands are at /rubric. New scans use the current active rubric; historical scans render against their original rubric.
Visit the scanner and submit a URL to generate a score. Every completed public scan creates a permanent score page and makes the domain eligible for ranking. There’s no application process and no editorial gate.
Add User-agent: AgentSpeedBot / Disallow: / to your robots.txt. On the next scan we honour it automatically and the public score page is replaced with a removal notice. See /bot.
Scan your dev-tool site to verify the integrations matrix + pricing units are agent-readable.
Side-by-side composite, sub-scores, and per-category winner. Permanent shareable URL.
Every check in the rubric has a remediation page with paste-ready snippets.
Crawler matrix, llms.txt analyzer, structured-data validator, and seven more.