Skip to content
Good for Bots

Developer Tools & APIs

Browse API and developer tool websites by AI visibility score. Inspect public scan findings and look for API references, examples and authentication guidance.

How websites are scoredSee the Developer Tools & APIs ranking

Filters · 2 active
Websites in the directory, with their Good for Bots score. Column headers sort the list.
SiteScore

goodforbots.com

View report for Good for Bots:

chromegoldmine.com

View report for Chrome Goldmine:

proxyjam.com

View report for ProxyJam:

amazingplugins.com

View report for AmazingPlugins:

sightradar.com

View report for SightRadar:

hypergsc.com

View report for HyperGSC:

nudgescout.com

View report for NudgeScout:

starkomand.com

View report for Starkomand:

devsexy.com

View report for DevSexy:

modeinspect.com

View report for Modeinspect:

rngdletool.com

View report for RNGdle Tool:

jevmodel.app

View report for JevModel:

tapetide.com

View report for Tapetide:

knobs.dev

View report for knobs:

stripe.com

View report for Stripe:

ihateimg.cv

View report for ihateimg.cv:

zipic.app

View report for Zipic:

cloudploy.com

View report for CloudPloy:

concretegravelcalculator.com

View report for Concrete Gravel Calculator:

ecommercedataapi.com

View report for Ecommerce Data API:

sshflow.com

View report for SSHFlow:

volanea.com

View report for Volanea:

citepulse-ai.run402.com

View report for CitePulse AI v4.0:

subtitle.im

View report for subtitle.im:

zerouter.ai

View report for Zerouter:

Promarks a Pro listing, in gold. Pro never changes a score or a place in the order.What Pro includes

Through a bot’s eyes

About Developer Tools & APIs

An API can be excellent and its website still leave an agent unsure how to begin. A product name and a dashboard screenshot do not explain what an endpoint does, where the reference lives, or which credentials a caller needs. The public site is the bridge between discovering a tool and deciding whether it fits a task.

This category includes developer services, SDKs, command-line tools and API products. Useful public material connects the overview to concrete examples, authentication guidance and limits. Machine-readable discovery can provide another entry point, but the explanation should remain intelligible to someone encountering the product for the first time.

A detected API catalog or authentication document helps locate an interface. Our scanner does not run the integration or establish permission to use it.

What to look for

Use these questions when reading the sites themselves. They are guidance for this category, not additional scoring checks.

A concrete first request
A worked example should show what goes in and what comes back. A feature list alone cannot tell an agent how the service fits a workflow.
Authentication explained
Public guidance should distinguish discovering an API from obtaining permission to call it, with a clear route to the appropriate credentials.
Limits where readers can find them
Usage limits, error handling and version policy belong near the reference. They affect whether an integration will work beyond its first request.
Discovery backed by documentation
Follow discovered catalogs and capability descriptions through to their references. A machine-readable entry is most useful when the surrounding documentation explains its boundaries.

Frequently asked questions

Do you call the API during a scan?

The scanner collects public web evidence and discovery documents. It does not run an authenticated integration or test the provider's business operations.

Does an API catalog add score points?

API Catalog is a capability in our rubric. A detected capability earns a badge, not points; the readability score is calculated separately.

Can a developer tool appear without a public API?

Yes. SDKs, local tools and developer services belong here too. Category membership does not assert that a public API exists.

Questions about scores, scans and listings in general are answered in the FAQ.