Sato Hub: Onchain Agents

{
  "id": "aix_f72c40be89",
  "name": "Sato Hub: Onchain Agents",
  "operator": "(unclaimed - source: registry-official · publisher: ai.satohub)",
  "description": "Search scored onchain-agent tooling: frameworks, MCP servers, wallets, x402 rails, deploy specs.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-10-22",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "blog-article",
    "github-ops",
    "inventory-check",
    "invoice-parsing",
    "market-data",
    "onchain-data",
    "token-swap"
  ],
  "protocols": {
    "mcp": "https://satohub.ai/api/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 3225,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-10-22T23:01:03.231Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://satohub.ai/mcp"
    },
    {
      "label": "repository",
      "url": "https://github.com/satohubai/onchain-agents"
    }
  ],
  "avatar": "https://github.com/satohubai.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/satohubai"
    }
  ],
  "profile": {
    "mcp_server": "onchain-agent-mcp-server",
    "mcp_version": "0.1.0",
    "tool_count": 48,
    "tools": [
      {
        "name": "onchain_agent_search_resources",
        "description": "USE WHEN you need to look up crypto-agent tooling (frameworks, MCP servers, wallets, payment rails, data tools) by name, chain, standard or what it does, or check that a specific project exists and is maintained. A daily-rebuilt directory, each entry scored from public evidence and linking to a citable page.\nNOT FOR a build goal in plain words such as \"a trading agent on Base\" (use onchain_agent_recommend_stack instead), a RUNNING agent to hire or pay (use onchain_agent_search_agents), a downloadable agent package (use onchain_agent_search_listings), what an agent skill touches (use onchain_ag"
      },
      {
        "name": "onchain_agent_get_resource",
        "description": "USE WHEN you need to judge one specific directory project: is it open source, still maintained, who is behind it, what does it support.\nNOT FOR a REGISTERED running agent (use onchain_agent_get_agent_passport instead), a published agent package (use onchain_agent_inspect_listing), install steps (use onchain_agent_get_deploy_spec), or finding a slug (use onchain_agent_search_resources first).\n\nRETURNS (json): { resource: {...full record incl. marketplace + liveness fields}, recent_activity: [...], agent_docs } by slug, optionally with recent releases and posts. `agent_docs` is where the project"
      },
      {
        "name": "search",
        "description": "USE WHEN you want one query box over Sato Hub, the daily-rebuilt index of what onchain and crypto AI agents are built from (frameworks, MCP servers, wallets, x402 and stablecoin payment rails, data tools), plus its dated answers, agent-economy numbers and wiki. Not for token prices, trading or investment advice.\nNOT FOR filtered or paginated directory queries (use onchain_agent_search_resources instead) or registered agents (use onchain_agent_search_agents).\n\nRETURNS (json): { results: [{ id, title, url }] }, at most 10, best first, from one query string; url is the canonical satohub.ai page t"
      },
      {
        "name": "fetch",
        "description": "USE WHEN you hold an id that `search` returned and want that record from Sato Hub, the daily-rebuilt index of what onchain and crypto AI agents are built from, as plain text to quote. Not for token prices, trading or investment advice.\nNOT FOR a directory slug (use onchain_agent_get_resource instead) or an id you made up (call `search` first).\n\nRETURNS (json): { id, title, text, url, metadata: { as_of, kind, sato_score?, source } }. text is plain prose to quote: for a listing, what it is, its category and chains, its Sato Score with the date (how open, active and verifiable it is — not a safet"
      },
      {
        "name": "onchain_agent_get_deploy_spec",
        "description": "USE WHEN a component has been picked (from onchain_agent_recommend_stack, onchain_agent_build_plan or a search) and the next step is installing it, once per pick, or you are about to write setup instructions and want steps checked against a clean install rather than copied from a README.\nNOT FOR choosing components (use onchain_agent_recommend_stack instead), whether an install command takes your key (use onchain_agent_check_install), or a full evidence list (use onchain_agent_preflight).\n\nRETURNS the deploy manifest for one resource by slug: runtime, install command(s), entry snippet, require"
      },
      {
        "name": "onchain_agent_recent_changes",
        "description": "USE WHEN asked what has changed recently across crypto-agent tooling, or what has happened to one specific project over time, and you want dated, attributable HEADLINE events (a human-readable feed). Omit slug for the SITE-WIDE feed; pass slug for ONE resource's history, the auditable Listing History.\nNOT FOR keeping a local copy in sync (use onchain_agent_get_changes instead, which returns added/updated/removed since a date) or a listing's daily check record and score series (use onchain_agent_get_listing_history).\n\nRETURNS (json): { scope, total, changes: [{ date, kind, slug, name, title, de"
      },
      {
        "name": "onchain_agent_list_categories",
        "description": "USE WHEN you need the valid category values before filtering onchain_agent_search_resources, or want to see how the crypto-agent landscape divides up by size.\nNOT FOR chain names (use onchain_agent_list_chains instead) or finding projects (use onchain_agent_search_resources).\n\nRETURNS (json): { total, categories: [{ name, count }] }, every resource category with counts, most populated first. Read-only.\n\nExample: {}"
      },
      {
        "name": "onchain_agent_list_chains",
        "description": "USE WHEN you need the valid chain names before filtering onchain_agent_search_resources, or want to know which chains have real agent tooling behind them rather than an announcement.\nNOT FOR category names (use onchain_agent_list_categories instead) or onchain agent counts per chain (use onchain_agent_get_agent_economy).\n\nRETURNS (json): { total, chains: [{ name, count }] }, every blockchain represented in the directory with resource counts, spotlight chains first (Base, Ethereum, Solana, COTI, Injective…). Read-only.\n\nExample: {}"
      },
      {
        "name": "onchain_agent_get_news",
        "description": "USE WHEN asked what is new or what shipped recently in crypto AI agents, and you want dated, source-attributed items rather than undated blog posts. Official releases (GitHub), project announcements, and reputable RSS, strongly filtered to the agent economy. Filter by kind (release/tweet/news/research) and/or chain; paginate via limit/offset.\nNOT FOR changes to the directory's own records (use onchain_agent_recent_changes instead) or a concept explainer (use onchain_agent_get_wiki_page).\n\nRETURNS (json): { total, count, offset, has_more, next_offset?, news: [{ kind, title, summary, url, source"
      },
      {
        "name": "onchain_agent_get_metrics",
        "description": "USE WHEN you need one current, citable headline figure for the onchain agent ecosystem rather than a number from an article of unknown age: the ERC-8004 Identity Registry registered-agent count (read directly from Ethereum mainnet) and the curated Top Project Tokens index (only tokens of directory-listed projects, never the whole agent-token category or its aggregate market cap).\nNOT FOR counts by venue, chain or stage (use onchain_agent_get_agent_economy instead), a time series (use onchain_agent_get_trend), or token prices for trading.\n\nRETURNS (json): { erc8004: { network, registered_agents"
      },
      {
        "name": "onchain_agent_get_wiki_page",
        "description": "USE WHEN asked to explain a crypto-agent concept (what x402 is, how agents hold wallets, what ERC-8004 does) and you want a sourced explainer you can cite. Find slugs with onchain_agent_list_wiki_pages.\nNOT FOR a specific project (use onchain_agent_get_resource instead) or how the Sato Score works (use onchain_agent_get_score_methodology).\n\nRETURNS (json): the full wiki page by slug: summary, why it matters, how it works, key components, examples, risks, related resources/pages. A near-miss slug that plainly means a page (\"what-are-erc-8004\" or the bare \"erc-8004\" for \"what-is-erc-8004\") serve"
      },
      {
        "name": "onchain_agent_search_agents",
        "description": "USE WHEN you need a RUNNING agent to work with, hire or pay (not a tool to build one with) and want to see who registered it, on which chain, and whether it accepts payment.\nNOT FOR tools to build an agent from (use onchain_agent_search_resources instead), one agent's full manifest (use onchain_agent_get_agent_passport with a slug from here), or a ranked pick for a task (use onchain_agent_route_agent).\n\nRETURNS (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Sear"
      },
      {
        "name": "onchain_agent_get_agent_passport",
        "description": "USE WHEN you are about to work with, pay or depend on a REGISTERED agent and want its published identity before committing. Find slugs with onchain_agent_search_agents.\nNOT FOR a project in the directory such as a framework or MCP server (use onchain_agent_get_resource instead; aixbt, almanak and coinbase-agentkit have no passport).\n\nRETURNS the full Sato Agent Passport manifest (sato.agent.manifest/v1) for one registered agent by slug: identity (sato_agent_id), agent types, chains, model/framework, the stack of Sato Hub directory resources it runs on, links, payment/x402 endpoint metadata, an"
      },
      {
        "name": "onchain_agent_recommend_stack",
        "description": "USE WHEN someone wants to build any onchain or crypto agent (\"Build any crypto agent\") and says what it should do in plain words: \"a trading agent on Base\", \"an ElizaOS agent that charges via x402\", \"a TypeScript agent with a policy-controlled wallet\". This is the FIRST call for a build goal: goal → stack here, then onchain_agent_get_deploy_spec once per pick → install steps.\nNOT FOR looking up one named project (use onchain_agent_search_resources instead), the same stack as one composed answer with deploy specs, Preflight and a first action (use onchain_agent_build_plan), or the runnable repo"
      },
      {
        "name": "onchain_agent_list_wiki_pages",
        "description": "USE WHEN you need the slug for a crypto-agent explainer before calling onchain_agent_get_wiki_page, or want to see which concepts have a sourced page you can cite.\nNOT FOR reading a page (use onchain_agent_get_wiki_page instead) or finding projects (use onchain_agent_search_resources).\n\nRETURNS (json): { total, pages: [...] }, every Onchain Agent wiki page with slug, title, keyword, summary and last_updated. Read-only.\n\nExample: {}"
      },
      {
        "name": "onchain_agent_get_changes",
        "description": "USE WHEN you keep a local copy of the directory and need only what moved since your last sync (machine-readable added / updated / removed), rather than re-fetching the whole catalog.\nNOT FOR a readable headline feed or one project's history (use onchain_agent_recent_changes instead), or the current state of one record (use onchain_agent_get_resource).\n\nRETURNS (json): what changed since a given date: additions, per-resource change events, and retirements. { since, until, window_days, next_since, counts:{added,changed,removed}, added:[...], changed:[{slug,name,url,events:[...]}], removed:[...],"
      },
      {
        "name": "onchain_agent_get_agent_economy",
        "description": "USE WHEN asked how big the onchain agent economy actually is (how many agents are really registered, launched, paying or trading) and you want measured chain reads instead of a figure from a deck or an announcement. Covers the agent venues Sato Hub tracks: registries, launchpads, payment rails and account infrastructure, measured weekly from public chain reads.\nNOT FOR a series over time (use onchain_agent_get_trend instead), one headline ERC-8004 count (use onchain_agent_get_metrics), or agents registered with Sato Hub (use onchain_agent_search_agents).\n\nRETURNS (json): { week, as_of, rules, "
      },
      {
        "name": "onchain_agent_search_skills",
        "description": "USE WHEN someone is about to install an agent skill and should know what it will touch first: keys, credentials, remote scripts, outbound hosts. Crypto-relevant agent skills from ClawHub and skills.sh, each with a static DISCLOSURE: hosts it contacts, whether it generates or handles private keys, whether it asks the user to paste a credential, whether it pipes a remote script into a shell, whether it grants itself unrestricted tools, whether it registers the agent with a third-party host, whether it schedules itself. Each flag carries evidence lines on the skill's page.\nNOT FOR finding framewo"
      },
      {
        "name": "onchain_agent_get_trend",
        "description": "USE WHEN the question is whether a measurement is going up or down (ANSWERS ONE QUESTION). Returns a bounded series (at most 30 points, default 8) for ONE venue, ONE chain and ONE stage from Sato Hub's own weekly (or daily) chain reads, each point with its date, value, sample_size and method.\nNOT FOR this week's numbers across venues (use onchain_agent_get_agent_economy instead) or one listing's score or check history (use onchain_agent_get_listing_history).\n\nPass stage (required). Venue is optional: name it to read exactly one series; omit it and a stage that only one venue reports is read fr"
      },
      {
        "name": "onchain_agent_compare_listings",
        "description": "USE WHEN the question is how two directory listings compare on the axes Sato Hub tracks for both (ANSWERS ONE QUESTION), e.g. \"AgentKit or Solana Agent Kit?\".\nNOT FOR a single project's detail (use onchain_agent_get_resource instead) or a ranked stack for a goal (use onchain_agent_recommend_stack).\n\nRETURNS the SAME derived table the /compare pages render — category, chains, interfaces, standards, open-source status, listing status, last activity, last release, install proof, verification, Sato Score, GitHub stars — every cell read off the live records, never typed.\n\nRULE ENFORCED: there is NO"
      },
      {
        "name": "onchain_agent_explain_number",
        "description": "USE WHEN the question is where a published Sato Hub number comes from (ANSWERS ONE QUESTION) and you need its method, sample and reproduce call before quoting it.\nNOT FOR fresh measurements (use onchain_agent_get_agent_economy instead) or how old a data surface is (use onchain_agent_get_data_freshness).\n\nRETURNS: for any https://satohub.ai/numbers/<slug> page { slug, page, question, method, window, reproduce, mcp_server, rules } — how the number is measured and the exact call that reruns it. Otherwise it returns one finding from the State of Onchain Agents report by slug — the figure with its "
      },
      {
        "name": "onchain_agent_get_score_methodology",
        "description": "USE WHEN you are about to describe, apply or compare the Sato Score — or when asked how to tell whether a crypto-agent project is real, maintained or open — so you quote the rubric instead of guessing it.\nNOT FOR one project's score (use onchain_agent_get_resource instead; its record carries the score) or a score's movement over time (use onchain_agent_get_listing_history with score_days).\n\nRETURNS the six components with their maximum points and what each measures, the tier cutoffs, what \"provisional\" means, what is deliberately NOT in the score, how it is computed and reproduced, and where a"
      },
      {
        "name": "onchain_agent_get_data_freshness",
        "description": "USE WHEN you are about to quote a Sato Hub number, score, count or feed item and want to know how old it is — or when a figure looks stale and you need to know whether the pipeline behind it is late.\nNOT FOR how a number is measured (use onchain_agent_explain_number instead) or what changed in the directory (use onchain_agent_recent_changes).\n\nCOVERS, per data surface (directory activity, news, Sato Score, liveness checks, snapshots, ERC-8004 counts, the weekly agent-economy measurements, x402, LP pools, skills, deploy verification and more): when it was last collected successfully, when a col"
      },
      {
        "name": "onchain_agent_search_listings",
        "description": "USE WHEN someone wants a ready-made onchain agent PACKAGE to download or fork rather than assemble one. Searches Sato Hub's published agent packages, each a public view of one sealed, immutable version: its task, inputs/outputs, required permissions, model support (\"configured, not evaluated\"), license, and evidence freshness for that exact digest.\nNOT FOR directory projects such as frameworks or MCP servers (use onchain_agent_search_resources instead), running agents to hire (use onchain_agent_search_agents), or generating a fresh repo from a goal (use onchain_agent_create_agent).\n\nRETURNS (j"
      },
      {
        "name": "onchain_agent_inspect_listing",
        "description": "USE WHEN you have a PACKAGE slug (from onchain_agent_search_listings) and need what it does, what it needs and what is on record about it before recommending a download or fork.\nNOT FOR directory listings such as a framework, MCP server or project (use onchain_agent_get_resource instead) or finding a package slug (use onchain_agent_search_listings).\n\nRETURNS the package's public fields only: task, description, creator display name, version digest and signing state, recipe, input/output schemas, required services and permissions, model support (\"configured, not evaluated\"), operating-cost basis"
      }
    ],
    "profiled_at": "2026-10-22T23:01:03.231Z"
  },
  "unreachable": false
}