Build guide
Build a treasury balance monitor for Base addresses that sends alerts
On Base, the top-ranked stack for this goal is Zerion (data & market feeds), optionally with Olas (Autonolas) (agent framework), as of 2026-10-01.
Ranked by Sato Score, liveness, a Sato Hub-reproduced install, the share of daily checks answered, and fit to what the goal names. A Sato Score measures how open, active and verifiable a project is; it is not a safety, quality or returns grade.
Derived from 436 listings by the same engine as the MCP tool onchain_agent_recommend_stack · picks last checked 2026-10-01
The stack, layer by layer
1. Data & market feeds
This job only reads. Prefer a source whose Sato Check line shows no key read, and do not hand a monitor a key it never uses.
Zerion Sato Score 85 · High
Sato Check (v1.9.1, 2026-09-26, declared+traced): Asks for a private key or seed phrase in its setup; not yet run with planted keys.
npm install -g zerion-cli· install reproduced by Sato Hub 2026-09-21 · Sato CheckSkim Sato Score 86 · High
Sato Check (v0.2.5, 2026-09-28, declared+traced+observed): Reads your key and signs locally — what a wallet does; a planted key was not observed leaving (during install and start-up in our sandbox; code paths that run later or on a trigger are not covered).
npx -y skim-mcp· install reproduced by Sato Hub 2026-09-25 · Sato Check
2. Agent frameworkoptional
Olas (Autonolas) Sato Score 87 · High
Sato Check (v2.2.9, 2026-09-29, declared+traced): No private-key read found in its setup or published code; not yet run with planted keys.
pip install open-autonomy[all]· install reproduced by Sato Hub 2026-09-21 · Sato CheckAlmanak Sato Score 83 · High
Sato Check (2026-10-01, declared): Key access unknown — we could not read this version.
pipx install almanak· install reproduced by Sato Hub 2026-09-21 · Sato Check
Left out on purpose
- A monitor only reads balances. It needs no signing key, and an alert bot should not be handed one it never uses.
- Balances are read directly over RPC or from a data feed; an MCP server adds an interface this job does not need.
Start from a generated repo
One command generates a runnable TypeScript repo from the treasury-monitor template, with a spending policy and a dependency lock. It targets a local fork by default, holds no key, and the goal is not stored.
npx create-sato-agent@0.1 "a read-only treasury balance monitor that reads onchain data and sends alerts" --framework plain-tsTemplates are re-checked every night. See the templates and their last result.
Install steps and checks
Each pick shows the first install line from its deploy spec and whether Sato Hub reproduced that install in a container or only parsed it from the project's docs. The Sato Check link under each pick opens what its code does with a key. For a fuller reading of any pick before you install, connect or pay, run Preflight.
An agent can pull this same stack, with install steps for every pick, in one call:
onchain_agent_build_plan {"goal":"a read-only treasury balance monitor that reads onchain data and sends alerts","chain":"Base"}Server: https://satohub.ai/api/mcp, no key.
What this does not cover
- Where the alerts go. Email, Telegram, a webhook or a pager is your channel; none of it is a directory listing.
- Which addresses to watch and at what thresholds. That list is yours, and so is the decision about what counts as unusual.
- Acting on an alert. This monitor is read-only on purpose. A guide that also moves funds is a different job with a different risk.
- An RPC provider. Reads need one; pick it on its rate limits and terms.
How to read the numbers
- A Sato Score measures how open, active and verifiable a project is. It is not a safety, quality or returns grade.
- A Sato Check line describes what was read and run, with its date and its limits. A missing reading is unknown, not clear.
- Unknown means Sato Hub holds no record. It does not mean something is wrong.
- This is a build guide. It is not trading, investment or legal advice.
- Sato Hub has no token. A token using the Sato name is not ours.