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 scored

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt4The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap4A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD4Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML1The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation2Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons3Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields1Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states4Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL4Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links4Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

Filters · 2 active

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt4The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap4A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD4Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML1The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation2Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons3Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields1Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states4Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL4Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links4Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

4 sites

WordPress

Websites in the directory, with their Good for Bots score. Column headers sort the list.
Site	Category	Score
Emailyy emailyy.online Free browser-based email tools for signatures, subject lines, HTML previews, and header analysis	Developer Tools & APIs	View report for Emailyy:
EnjoySEOS enjoyseos.online Free online toolkit for SEO previews, schema generation, sitemaps, and redirects	Developer Tools & APIs	View report for EnjoySEOS:
Jomatter jomatter.online Free browser-based tools for formatting, validating, and testing HTML, CSS and JavaScript	Developer Tools & APIs	View report for Jomatter:
SpeeJax speejax.online Free browser-based tools to minify code, compress images, and optimize website performance	Developer Tools & APIs	View report for SpeeJax:

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.