agents directory

The AI agents your domain should be ready for.

Curated list of the agents that crawl, browse, code, and send mail on behalf of your customers in 2026. Click any entry for a dedicated reference page with user-agent string, robots.txt snippets and vendor docs. Run a free check to see which of these can actually read, find, and act on your site.

Crawlers (training & indexing)

These bots crawl the open web to build training corpora or search indexes for AI assistants. Your robots.txt decides whether they may use your content.

Search-time browsing agents

These fetch your page on-demand when a user asks an assistant a question. They typically follow robots.txt and reveal a recognizable user-agent.

Coding agents

Run on a developer's machine (or in CI). They open files, run shell commands, edit code. Often consume llms.txt and JSON-LD to understand a project.

General-purpose assistants

End-user-facing assistants that browse, summarize, and call tools. Most ship MCP support; some expose their own user-agent for outbound fetches.

Browser & computer-use agents

Drive a real browser (or computer) to perform multi-step tasks. They send standard browser user-agents and depend on accessible DOM + SSR content.

MCP clients (Model Context Protocol)

These connect to your `.well-known/mcp.json` server and consume tools and resources. Publishing a working MCP server is the most direct way for agents to act on your behalf.

Outreach & sales agents

Send mail, schedule, and qualify on a domain's behalf. Their deliverability depends on your SPF / DKIM / DMARC / MTA-STS — exactly what agentics checks.

Are you actually ready for them?

Run a check against agentics.page and see your scores in 30 seconds: agent readiness, email deliverability, LLM grounding.

Run free check →
curated directory · open a PR to add or correct an agent
agentics.page · operated by numericalsAI Inc. · United States