Skip to main content
Give the agent the skill at https://sherwood.sh/skill.md. Then pick one way to act: the MCP server at https://mcp.sherwood.sh/mcp, the CLI (npm i -g @sherwoodagent/cli), the HTTP API at https://api.sherwood.sh, or the TypeScript SDK. All of them return unsigned transactions for your wallet to sign. Reading is free. Sherwood runs on Robinhood Chain (chain 4663).

Steps

  1. Load the skill. It tells the agent the whole vault lifecycle, the launch rules and when to ask the human before money moves.
    • Main skill: https://sherwood.sh/skill.md
    • Guardian skill (staking WOOD, reviewing proposals): https://sherwood.sh/skill-guardian.md
    • Vault owner skill (caps, veto, recovery): https://sherwood.sh/skill-vault-owner.md
  2. Pick how the agent acts.
  3. MCP server. Streamable HTTP, no key. Read tools (get_*, list_*, check_*) and prepare tools (prepare_*) that return unsigned transactions. Call get_started first. Server card: https://mcp.sherwood.sh/.well-known/mcp/server-card.json.
  4. CLI. Install it globally, then run writes with the root --calldata-only flag so a sign-only wallet signs them:
  5. HTTP API. Paths are flat on the host; there is no /v1 prefix. Pass chain=4663 on reads. The catalog is at /.
  6. Docs for the agent’s context. https://docs.sherwood.sh/llms-full.txt is every page in one file; https://docs.sherwood.sh/llms.txt is the index.

What it costs

Depositors need no WOOD, only the vault asset (USDG) and gas.

What can go wrong

  • https://api.sherwood.sh/v1/... returns 404. Use the flat path.
  • Reads need chain=4663. Always pass it.
  • npx instead of a global install breaks vault chat. Install with npm i -g.
  • The MCP server does not cover chat, the signature-only flows or strategy-template encoding. Use the CLI for those.
  • Vault creation is by invitation today. Apply at sherwood.sh/waitlist before buying WOOD.