Sato Hub: Onchain Agents MCP

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. NOT FOR a build goal in plain words such as "a trading agent on Base" (use onchain_agent_r

USE WHEN you need to judge one specific directory project: is it open source, still maintained, who is behind it, what does it support. NOT 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). RETU

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. NOT FOR filtered or paginated directory queries (use onchain_agent_search_resources in

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. NOT FOR a directory slug (use onchain_agent_get_resource instead) or an id you made up (call search first). RETURNS (json): { id, title, text, url, metadata: { a

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. NOT FOR choosing components (use onchain_agent_recommend_stack instead), whether an install command takes your

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. NOT FOR keeping a local copy in sync (use onchain_agent_get_changes instead, which returns added/

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. NOT FOR chain names (use onchain_agent_list_chains instead) or finding projects (use onchain_agent_search_resources). RETURNS (json): { total, categories: [{ name, count }] }, every resource category with counts, most populated first. Read-

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. NOT FOR category names (use onchain_agent_list_categories instead) or onchain agent counts per chain (use onchain_agent_get_agent_economy). RETURNS (json): { total, chains: [{ name, count }] }, every blockchain repre

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. NOT FOR changes to the directory's own records (use onc

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). NOT FOR counts by

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. NOT FOR a specific project (use onchain_agent_get_resource instead) or how the Sato Score works (use onchain_agent_get_score_methodology). RETURNS (json): the full wiki page by slug: summary, why

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. NOT 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_ag

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. NOT 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). RETURNS the full Sato Agent Passport manifest (sato.agent.manife

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. NOT FOR looking up on

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. NOT FOR reading a page (use onchain_agent_get_wiki_page instead) or finding projects (use onchain_agent_search_resources). RETURNS (json): { total, pages: [...] }, every Onchain Agent wiki page with slug, title, keyword, summary and la

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. NOT 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). RETURNS (json): what changed since a given da

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. NOT FOR a series over time (use onch

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

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. NOT FOR this week's numbers across venues (use onchain_agent_get_agent_economy instead) or one listing's s

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?". NOT FOR a single project's detail (use onchain_agent_get_resource instead) or a ranked stack for a goal (use onchain_agent_recommend_stack). RETURNS the SAME derived table the /compare pages render — category, chains, interfaces, standards,

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. NOT FOR fresh measurements (use onchain_agent_get_agent_economy instead) or how old a data surface is (use onchain_agent_get_data_freshness). RETURNS: for any https://satohub.ai/numbers/<slug> page { slug, page, question, method, window

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. NOT 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). RETURN

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. NOT FOR how a number is measured (use onchain_agent_explain_number instead) or what changed in the directory (use onchain_agent_recent_changes). COVERS, per data surface (directory activity, news, Sa

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. NOT FOR directory projects such as frameworks or

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. NOT 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). RETURNS the package's public fields only: task,

USE WHEN the question is whether a listing has been answering Sato Hub's daily checks and whether its tool inventory has moved (ANSWERS ONE QUESTION), or how its Sato Score has moved day by day. NOT FOR a feed of events across projects (use onchain_agent_recent_changes instead) or the listing's current record (use onchain_agent_get_resource). RETURNS a bounded 30-day shape from the listing's obse

USE WHEN you are about to install a package, clone a repo, connect to an MCP endpoint, pay an agent, or trade a token, and you want to know what is on record about it FIRST — every evidence line, with the field it was read from and its date. Pass exactly one of repo, package, endpoint, agent, token, skill, x402 or address. NOT FOR a stack pick's summary (onchain_agent_recommend_stack and onchain_a

USE WHEN you are about to install a crypto package, MCP server or skill and want to know what it can do with your keys and funds: before npm/pnpm/yarn/bun add, npx -y, pip install, uvx or claude mcp add, or before pasting an {"mcpServers": …} config. NOT FOR a token, repo, endpoint or agent you were handed (use onchain_agent_preflight instead), install steps for a stack pick (use onchain_agent_g

USE WHEN an agent is about to pay or transfer to an address: an x402 payTo, a treasury sweep, a top-up. Pass the chain and the recipient; add the token, the origin whose 402 named the address and the paying wallet for a fuller reading. Sato Scan answers five questions, each with its own date and gap. NOT FOR checking a package, repo, token, endpoint or agent (use onchain_agent_preflight instead; i

USE WHEN an agent wants a swap QUOTE with the venue chosen by liveness, verification and price and the fee disclosed. Asks every aggregator adapter that quotes on the chain, in parallel, and returns the chosen venue's quote and calldata. NOT FOR a swap checked against token, venue and recipient verdicts and a spending policy, with a simulated unsigned transaction and a receipt (use onchain_agent_s

USE WHEN an agent needs another agent for a task and wants the pick explained by registration, answering service, feedback and liveness. Candidates are the listed Sato Agent Passports; the top 3 by the static ranking get one live MCP handshake before the pick is made. NOT FOR browsing registered agents with filters (use onchain_agent_search_agents instead) or one agent's manifest (use onchain_agen

USE WHEN an agent or a builder is about to launch a token and wants the venue chosen on published facts, with the fee disclosed before anything is signed. Venues covered: Clanker v4, Bankr, Virtuals, Zora creator coins. NOT FOR a swap (use onchain_agent_route_swap or onchain_agent_swap instead), a liquidity pool (use onchain_agent_route_lp), or generating a launch-prep repo (use onchain_agent_crea

USE WHEN someone describes the onchain agent they want and needs ONE composed answer that goes from goal to install steps (stack, deploy specs, Preflight, first action, open questions) rather than advice. NOT FOR only the ranked stack (use onchain_agent_recommend_stack instead, the lighter first call), a plan plus a pointer to the repo generator (use onchain_agent_scaffold_plan), or the runnable r

USE WHEN an agent is deciding which Uniswap pool and fee tier to provide liquidity to for a pair Sato Route already quotes, and wants the observed readings rather than an opinion. NOT FOR a swap (use onchain_agent_route_swap or onchain_agent_swap instead) or a token launch (use onchain_agent_route_launch). RETURNS every v3 pool the weekly LP lane found across the four standard fee tiers, each wit

USE WHEN someone wants the code for an onchain agent, not advice: describe the goal and get a runnable TypeScript repo generated from a template that is re-checked every night. Same handler as POST /api/create and the create-sato-agent CLI. NOT FOR choosing a stack or advice (use onchain_agent_recommend_stack or onchain_agent_build_plan instead) or a plan with no repo (use onchain_agent_scaffold_p

USE WHEN a plan has been agreed and the next question is which repository to start from. Builds the plan (same brain as onchain_agent_build_plan) and returns it with a create pointer to onchain_agent_create_agent, which generates the runnable repo from a nightly-checked template. NOT FOR the full plan with deploy specs and Preflight on every pick (use onchain_agent_build_plan instead) or the

USE WHEN an agent (or the person it works for) wants to be told if something in its stack stops checking out — rather than re-running a Preflight on a schedule of its own. This WRITES one subscription row. NOT FOR a one-off check now (use onchain_agent_preflight instead) or a record's change history (use onchain_agent_recent_changes). Goes through the SAME path the public form uses: same validatio

USE WHEN an agent has found, built or maintains a crypto-agent project that is not in the directory and wants it considered. NOT FOR correcting a listing that already exists (that goes through the claim flow on its page), checking whether a project is listed (use onchain_agent_search_resources first), or registering a running agent (use onchain_agent_register_agent). This WRITES: it files the sam

USE WHEN an agent wants a public, machine-readable identity: an Agent Passport at satohub.ai/agents/<slug> plus a manifest at /api/agents/<slug>/manifest that another agent can read before deciding to work with it. This WRITES a passport. NOT FOR submitting a project, framework or tool to the directory (use onchain_agent_submit_project instead) or reading a passport (use onchain_agent_get_agent_pa

USE WHEN an agent is about to swap and wants the venue chosen, the fee disclosed, and the trade CHECKED before anything is signed. Two modes: recommend returns the choice, the fee sentence and the verdicts and NEVER a transaction; build-tx returns an UNSIGNED transaction, and only when the gate allowed it and a simulation did not revert. build-tx WRITES a receipt row. NOT FOR a plain quote w

USE WHEN a person or an agent has dropped a contract address, a Solana mint or a link and the next step needs to know what it IS before anything else happens: chain, address, name, symbol, decimals, token program, the main pool and that pool's liquidity, and the token's USD price. Read-only. NOT FOR what the chain says about the token's authorities, extensions and liquidity (use onchain_agent_pref

USE WHEN an agent needs a paid API or data service it can call and pay per request with x402, and wants the ones with evidence behind them first. Find a paid API/data service an agent can call and pay per request with x402: market data, onchain data, web data, search, inference, security checks, identity lookups, dev tools and more. Describe the need in plain words; optional category, chain and ma

USE WHEN you are about to write, fix or upgrade code that imports a crypto or agent SDK (viem, ethers, @solana/web3.js, x402, ...) and need to know which major line is current, whether the package or version you were taught is legacy or deprecated, what replaces it, and what breaks on the way. NOT FOR choosing a framework, wallet or payment rail for a build goal (use onchain_agent_recommend_stack

USE WHEN you need the canonical address or id of something on a chain and want it with its source and date instead of from memory: a protocol's deployment (Uniswap Permit2, a Safe singleton, Multicall3, the ERC-4337 EntryPoint, an ERC-8004 registry), the USDC contract and CCTP domain Circle states for a chain, an x402 SDK's default stablecoin, or a chain's registry entry. NOT FOR a whole-chain rea

USE WHEN you are about to build for or deploy to a chain and want its dated facts in one call: registry entry, USDC and CCTP domain, ERC-8004 registry deployment, which public RPC endpoints support state-override calls and eth_simulateV1, which x402 facilitators list it, and reported activity. NOT FOR one contract's address (use onchain_agent_get_contract_facts instead), the facilitator roster acr

USE WHEN an agent has to pay or charge with x402 and needs to know which facilitator lists a chain, a scheme and a protocol version, how recently each one actually answered, and which ones could not be read (key wall, unreachable), so "none lists it" is never mistaken for "all were checked". NOT FOR finding a paid API to call (use onchain_agent_search_resources instead, with standard "x402"), one