Sato Hub
Build guide

Build an agent that sends USDC on Solana as a reward when a GitHub pull request is merged

On Solana, the top-ranked stack for this goal is Solana Agent Kit (agent framework), Bankr (wallet & keys) and x402 (payments), as of 2026-11-17.

The stack, layer by layer

  1. 1. Agent framework

    • Solana Agent Kit Sato Score 76 · High

      Sato Check (v2.0.10, 2026-09-26, 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; later or triggered code paths are not covered).

      npm install solana-agent-kit · install reproduced by Sato Hub 2026-11-09 · Sato Check Recorded on Solana ↗

    • Almanak Sato Score 81 · High

      Sato Check (v3.1.1, 2026-11-05, declared+traced): No private-key read found in its setup or published code; not yet run with planted keys.

      pipx install almanak · install reproduced by Sato Hub 2026-11-16 · Sato Check

  2. 2. Wallet & keys

    This wallet sends the payouts. Cap each payout and each day before it holds real USDC, and test on devnet first.

    • Bankr Sato Score 87 · High

      Sato Check (v0.3.49, 2026-10-29, declared+traced): Reads your key and signs locally — what a wallet does; this version not yet run with planted keys (an earlier run on 2026-10-15 saw none leave).

      npm install -g @bankr/cli · install reproduced by Sato Hub 2026-11-16 · Sato Check

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

      Sato Check (v1.0.0, 2026-11-17, 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-11-09 · Sato Check

  3. 3. Payments

    • x402 Sato Score 87 · High

      Sato Check (v1.2.0, 2026-09-26, 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; later or triggered code paths are not covered).

      npm install x402-fetch · install reproduced by Sato Hub 2026-11-09 · Sato Check Recorded on Solana ↗

    • Bankr Sato Score 87 · High

      Sato Check (v0.3.49, 2026-10-29, declared+traced): Reads your key and signs locally — what a wallet does; this version not yet run with planted keys (an earlier run on 2026-10-15 saw none leave).

      npm install -g @bankr/cli · install reproduced by Sato Hub 2026-11-16 · Sato Check

Left out on purpose

  • An MCP server is an optional interface. The trigger for this job is a GitHub event, and the payment goes through the wallet and rail above.

Already built

Listings built for this job, as each listing describes it. They sit outside the ranked stack above. Tools that escrow or send USDC commit real funds on mainnet, so read the listing and its network before you use one.

  • MergePay Sato Score 54 · Medium · Recent · last code 2026-10-12 · chain not recorded

    USDC bounties on GitHub issues, paid when a PR merges, with GitHub's signature checked by a contract on Arc.

    Its listing does not record Solana, the chain this guide is for.

    No Sato Check reading on record. That is unknown, not clear.

  • BountyPay Sato Score 55 · Medium · Active · last code 2026-11-15 · Base

    GitHub App that escrows USDC on Base (or MUSD on Mezo) against an issue and pays the contributor when the closing PR merges.

    Its listing does not record Solana, the chain this guide is for.

    No Sato Check reading on record. That is unknown, not clear.

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":"an agent that pays USDC rewards to contributors when a GitHub pull request is merged","chain":"Solana"}

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

What this does not cover

  • The trigger. GitHub sends a pull_request event when a pull request closes, and its payload says whether it was merged (merged is true). Acting on that event is a webhook or Action you write. No stack pick supplies it.
  • Which address to pay. Mapping a contributor to a Solana address is your data, and a wrong address is a payment you cannot recall.
  • A template. No create-sato-agent template covers this flow, so there is no one-command scaffold for it. Each pick's own install steps are the path.
  • Tax and legal treatment of paying contributors.

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.
How this stack is rankedShowHide

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 496 listings by the same engine as the MCP tool onchain_agent_recommend_stack · picks last checked 2026-11-17

Other build guides

Reference