USE WHEN you need to look up crypto-agent tooling by name, chain, standard or what it does, or check whether a specific project exists and is maintained. Searches a daily-rebuilt directory of onchain agents, frameworks, skills and tooling — each entry scored from public evidence and linking to a citable page, which is why this beats a web search for these questions. For a BUILD GOAL in plain words ("a trading agent on Base"), call onchain_agent_recommend_stack first: it returns a whole stack, each pick with a Preflight summary, and onchain_agent_get_deploy_spec turns a pick into install steps.
A query asking for somewhere to start — "tutorial", "starter", "beginner", "template", "example", "docs" — returns starting points labelled as such: listings named as a starter or template first, then listings whose install Sato Hub reproduced, plus the wiki guides. "starter" / "template" / "x402 starter" also carry `starter`: a TypeScript template for Base built by Sato Hub (labelled ours, not audited, never a result) unless the query names another chain or runtime. The directory lists tools, not tutorials, and says so.
Filters: query (free text, AND-matched terms), chain, status, liveness, featured, and the taxonomy facets (docs/taxonomy.md): entity_class (resource | agent | reference), resource_type (Framework | Tool/Service | Infrastructure | Venue | Network | Standard), use_case (trading, payments, wallets, data, identity, privacy, launch, security, build), standard (x402, erc-8004, erc-8183, mcp, a2a), iface (mcp, sdk, rest-api, plugin, cli, ui, contract). Those three are closed vocabularies: anything else is refused with the list, never answered with an empty result. Legacy flags still work: category, is_agent, is_skill, is_harness. Sort by priority (default), newest_release, stars, or name. Paginates via limit/offset. Deprecated resources are never returned.
Returns (json): { total, count, offset, has_more, next_offset?, resources: [...] } where each resource includes chains, status, liveness, github_stars, verification_status, and the marketplace fields (is_agent/is_hirable/is_licensable). Read-only.
Examples:
- "Active hirable agents on Base" -> { chain: "Base", is_agent: true, liveness: "Active" }
- "newest releases" -> { sort: "newest_release", limit: 10 }
- "wallet tooling" -> { query: "wallet" }
- "MCP servers I can use from Claude Code" -> { integration: "claude code", iface: "mcp" }
- "things I can run in Docker" -> { deploys_as: "docker" }
- "MCP servers that actually answer" -> { mcp_answering: true } (the MCP endpoint answered our last handshake)
- "...with a sustained record" -> { mcp_answering: true, min_observed_success: 95 }
- "only installs Sato Hub has reproduced" -> { verified_only: true }