agentspeed.
Leaderboards

API products leaderboard

0 domainsupdated every 5mno scans yet

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.

Not enough scan data yet.

We surface only real, completed public scans. Once enough api products domains have a public score on AgentSpeed, this leaderboard fills in automatically.

Scan your site →
What makes a site agent-ready in this category

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.

Common failures
failure 01

Per-call pricing buried in calculator

When pricing requires interaction with a JS slider, agents cannot quote it. Show explicit price-per-call / token / month tables in HTML.

failure 02

Auth docs assume context

When the auth section says "use your API key" without a HOW, agents cannot generate self-serve guidance for users.

failure 03

No OpenAPI spec link

Without a discoverable OpenAPI/Swagger document, agents cannot reason about endpoints programmatically.

failure 04

Sandboxed examples that fail

When the "Try it" widget breaks for unauthenticated users, agents see broken curl commands and assume the API is broken.

Best practices
  1. 01Publish a public OpenAPI / GraphQL schema at a stable URL.
  2. 02Show per-call / per-token / per-month pricing as parseable text, not in a calculator.
  3. 03Declare auth scheme at the top of the docs (API key vs OAuth vs mTLS).
  4. 04List supported SDKs / languages with linkable per-language quickstart pages.
  5. 05Publish /llms.txt with API, SDKs, Pricing, Status, Changelog sections.
How this is computed

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.

FAQ

How are scores calculated?

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.

How do I get my domain on the leaderboard?

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.

How do I remove my site?

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.

Improve your own site
Run free scan

Scan your API site to see if agents can identify the auth method + pricing model.

Compare your site

Side-by-side composite, sub-scores, and per-category winner. Permanent shareable URL.

Browse fixes

Every check in the rubric has a remediation page with paste-ready snippets.

All free tools

Crawler matrix, llms.txt analyzer, structured-data validator, and seven more.