EarnClaw vision
Why EarnClaw exists, how finance agents are organized in the workspace, and how teams scale from one agent to a fleet.
Onchain finance is moving toward operator-first automation. Running agents safely is still fragmented: strategy code, wallets, schedules, policy checks, and execution often live in different tools. EarnClaw is the workspace that brings those pieces together so you can design, deploy, fund, and monitor finance agents in one place.
Jeff's first live protocol operations proved an AI operator can run real capital with high uptime. EarnClaw packages the lessons from that era into a product other teams can use without rebuilding the stack from scratch.
Why EarnClaw is needed
| Problem today | What EarnClaw provides |
|---|---|
| One-off prompts and scripts | Reviewed templates with defined strategies and guardrails |
| Wallet and signing scattered across tools | Agent wallets with scoped delegation and expiry |
| No standard safety review before an onchain action | Policy checks that stop blocked actions and explain why |
| Hard to audit what an agent tried | Run history, diagnostics, and billing in one dashboard |
| Each venue wired by hand | Supported integrations for trading, yield, and prediction |
EarnClaw is not a chat surface. It is the control plane for autonomous finance operations: you keep wallet ownership and risk limits; EarnClaw hosts schedules, runtime health, and the path from decision to execution.
Built like finance infrastructure, not a chatbot
Giving an AI a prompt and a set of tools is not enough when real capital is involved. Operators need to know what will run, what changed, what the agent may do, and why an action executed or stopped.
EarnClaw combines defined strategy releases with limits enforced outside the agent itself. Supported launch paths are evaluated before release, and each cycle produces a record you can review.
You know exactly what is running
The agent decides, the rules protect
Tested before it trades
A record you can review
This is what it takes to run agents with real money. Delegate with limits, verify everything.
Three finance agent lanes
EarnClaw organizes agents around three lanes. Each lane has evaluated templates, runtime wiring, and observability hooks.
| Lane | What agents do | Example venues |
|---|---|---|
| Trading | Spot and perps execution on schedules or signals | Multi-chain EVM spot (aggregated DEX routing, millions of tokens), Hyperliquid perps, testnet venues where enabled |
| Yield | Vault and funding discovery, allocation, rebalance | Vaults.fyi, Yield.xyz, major lending protocols |
| Prediction | Signal-driven participation in binary markets | Polymarket-style markets where enabled |
You choose the lane in the new-agent wizard. The wizard only shows template and framework combinations that pass EarnClaw launch checks for your org.
How agents are organized in EarnClaw
Everything attaches to an org. Billing, deploy limits, and team access are org-scoped. See Organizations for how teams operate multiple agents. Under each org you run one or more agents:
On each cycle the agent reads current information, applies the template rules, and decides whether to act or wait. Safety checks run before an onchain action. Blocked actions appear in run history with an explanation.
For integration and execution details, see Integrations at runtime.
A typical agent cycle
| Step | Where you see it |
|---|---|
| Schedule and health | Agent detail, runtime diagnostics |
| Decision and supporting information | Run log |
| Onchain receipts and allowance usage | Run history; runtime plan in Settings |
| Org usage and plan limits | Billing |
| Org capital and balance history | Organization analytics |
See Observability and Dashboard map.
How teams scale
See Organizations for the org model and fleet operations.
Start with one agent. Pick a template, complete the wizard, activate a runtime plan, fund the wallet, and confirm a successful cycle in run history.
Add agents in the same org. Each agent gets its own wallet, delegation, and schedule. Workspace limits set how many agents can run at once. See Pricing overview.
Standardize with templates. Reuse reviewed templates and guardrails across agents. Builder publishing and marketplace features will appear in the docs when they are available.
Operate a fleet. Use consistent guardrails across agents, review blocked actions centrally, and adopt template updates when they are available. Higher workspace tiers add deploy headroom and early product lanes. See Pricing overview.
What changed from Jeff v1
Jeff v1 focused on one autonomous protocol CEO: liquidity, epochs, and gauge operations on Base. That run proved the operating model and surfaced what production agents need: mandate clarity, guardrails, and repeatable schedules.
EarnClaw v2 generalizes that into a workspace any team can use: trading, yield, and prediction agents with delegation, safety checks, and run history built into the operating flow.
The original Jeff CEO launch film lives on History.
Start building
- What is EarnClaw — product summary
- Organizations — billing scope and fleet scale
- Create your first agent — wizard walkthrough
- Fund and run — wallet, runtime plan, execution allowance