Products consumed by other software: usage-based, per-call, per-token, or per-month pricing. Agents read your reference, auth docs, and pricing to self-serve.
API products are consumed by other software, but their site is consumed by humans (and agents acting on their behalf) deciding whether to integrate. The decision turns on three signals: per-call pricing transparency, auth-method clarity, and language / SDK coverage.
When pricing requires interaction with a JS slider, agents cannot quote it. Show explicit price-per-call / token / month tables in HTML.
When the auth section says "use your API key" without a HOW, agents cannot generate self-serve guidance for users.
Without a discoverable OpenAPI/Swagger document, agents cannot reason about endpoints programmatically.
When the "Try it" widget breaks for unauthenticated users, agents see broken curl commands and assume the API is broken.
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 API site to see if agents can identify the auth method + pricing model.
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.