Can Agents Use

Find tools an AI agent can actually use.

Can Agents Use is a public, file-backed directory of APIs, CLIs, MCP servers, browser-operable products, pricing pages, docs, sandboxes, and account setup flows. The website is the live searchable surface. This README is the GitHub surface: a compact map of the project, the data, and the agent-facing interfaces.

What Is In The Catalog

The catalog is generated from data/tools and data/taxonomy.json, then exposed through the website, API, MCP endpoint, CLI, and LLM-friendly Markdown exports.

For current catalog contents, use the live search at canagentsuse.com or fetch /api/agent/catalog.

Every tool record is scored from evidence, not vibes. A good record answers:

• Can an agent operate it through an API, CLI, MCP server, or browser?
• Are docs, pricing, auth, and account setup clear enough to automate safely?
• Is there a sandbox, test mode, local mode, preview environment, or dry run?
• What should a human review before production use?

Features

• Fast searchable directory for agent-friendly software.
• Cmd-K style search for tools, categories, and capability signals.
• Category and capability filtering for broad comparisons.
• Tool detail pages with score breakdowns, evidence links, and limitations.
• Public API routes for agents and scripts.
• Read-only MCP-style JSON-RPC endpoint.
• LLM-friendly Markdown exports.
• JSON catalog stored directly in the repo.
• JSON Schema and audit scripts for safer contributions.
• GitHub pull request and agent-prompt submission flow.

Agent-Readiness Signals

The catalog tracks eight normalized signals:

Scoring Model

Scores are out of 100 and are derived from the evidence in each tool record.

The website keeps the score compact. Agent surfaces expose the detailed scoreBreakdown object.

Launch Score Model

launchScore is a secondary ranking signal used after agent readiness. It is