Build a Base trading agent that swaps USDC for ETH when a price signal fires

The stack, layer by layer

1. 1. Agent framework

   • Almanak 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

   • ElizaOS Sato Score 87 · High

     Sato Check: not yet read. Not key- or fund-bearing by its category, standards or setup.

     bun add -g elizaos@beta · install reproduced by Sato Hub 2026-09-21 · Sato Check

2. 2. Wallet & keys

   This wallet signs the swaps. Set a per-trade and a daily cap before it holds real USDC, and test on a local fork or a testnet first.

   • Bankr Sato Score 87 · High

     Sato Check (v0.3.43, 2026-09-30, 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).

     npm install -g @bankr/cli · install reproduced by Sato Hub 2026-09-21 · Sato Check

   • Trust Wallet Agent Kit (TWAK) Sato Score 87 · High

     Sato Check (v0.20.0, 2026-09-26, declared+traced): No private-key read found in its setup or published code; not yet run with planted keys.

     npm install -g @trustwallet/cli # binary: twak · install reproduced by Sato Hub 2026-09-21 · Sato Check

3. 3. Trading venue & execution

   • 1inch Sato Score 75 · High

     Sato Check: no published package on record to read (a hosted service, remote endpoint, git clone or skill).

     claude mcp add --transport http --header "Authorization: Bearer YOUR_API_KEY" --scope user 1inch-business https://api.1inch.com/mcp/protocol · install steps self-reported by the project, not reproduced · Sato Check

   • dYdX Sato Score 83 · High

     Sato Check (v3.6.0, 2026-09-28, declared+traced+observed): Asks for a private key or seed phrase in its setup; 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).

     npm install @dydxprotocol/v4-client-js · install steps self-reported by the project, not reproduced · Sato Check

4. 4. Data & market feeds

   • 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 Check

   • Skim 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

Start from a generated repo

One command generates a runnable TypeScript repo from the base-guarded-trader 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 Base trading agent that swaps USDC for ETH when a price signal fires" --framework plain-ts

Templates 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 Base trading agent that swaps USDC for ETH when a price signal fires","chain":"Base"}

Server: https://satohub.ai/api/mcp, no key.

What this does not cover

• The signal itself. Where the price signal comes from, and when it should fire, is your strategy. Nothing here rates or recommends one.
• Sizing, slippage and execution quality. The guide ranks tools by evidence about the tool, not by how well a trade executes.
• Returns. A Sato Score says how open, active and verifiable a project is. It says nothing about whether an agent makes money.

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.

Other build guides

• Build a treasury balance monitor for Base addresses that sends alerts
• Build an agent that sends USDC on Solana as a reward when a GitHub pull request is merged
• Build an agent that pays for APIs with USDC on Base