What is EarnClaw

EarnClaw is the workspace to create, deploy, fund, and monitor finance agents — with validated trading, yield, and prediction templates, hosted runtimes, and market data integrations.

EarnClaw is where you ship finance agents: pick a template, choose a runtime (Hermes, OpenClaw, or Claude), set guardrails, and operate from one dashboard.

You get certified strategy packs, org policies, wallet delegation, run history, and billing in one place. Every venue and data integration your agent uses routes through the Thirdfy action catalog, called from hosted runtimes via the Thirdfy Agent CLI or Thirdfy MCP. You do not rebuild execution rails or wire providers one by one.

We believe autonomous agents will reshape how finance runs: execution, risk, and operations move from manual clicks to governed, repeatable cycles. EarnClaw is built for that shift with production-grade deployment frameworks, hosted runtimes, policy guardrails, and LLM decision layers that fail closed when preflight does not pass.

How EarnClaw is built

Frameworks

Hermes, OpenClaw, and Claude managed agents. EarnClaw hosts schedules, health, and the path from decision to execution so you operate agents, not servers.

Guardrails and preflight

Template policy, delegation scopes, notional caps, venue allowlists, and kill switches run before any onchain step. Failed checks log a skip reason instead of silent failure.

LLM decision layer

Each cycle refreshes evidence, applies the template schema, and produces an execute-or-skip decision you can audit in run history. Model choice stays inside your org plan and template rules.

Certified templates

Strategy packs, adapters, and observability ship together. The wizard only lists template and framework pairs that pass EarnClaw launch checks for your org.

Professional agents in three lanes

EarnClaw ships validated agents in the lanes finance teams actually run today. Trading, yield, and prediction venues all use the same Thirdfy catalog surface (Agent CLI on Hermes and OpenClaw, MCP on Claude managed). Prediction today means hosted Polymarket signal agents on Hermes. Venue setup, funding, and CLOB readiness are covered in Thirdfy Polymarket integration.

Trading — spot and perps

Spot swaps across major EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, and more) through aggregated DEX routing with access to millions of tokens, plus perps on Hyperliquid where the pack is enabled. Schedules, signals, and guardrails apply before any trade intent runs.

Yield — spot and vaults

Discovery, allocation, and rebalance across major yield venues. Vault optimizers use certified packs so the agent moves capital on policy, not ad-hoc prompts.

Prediction — Polymarket

Polymarket signal agents for finance and crypto topics. Each cycle refreshes market context, the LLM scores edge versus implied odds, and recommends place, cancel, or skip inside your template ceilings. Orders run only after wallet setup, CLOB readiness, and preflight pass.

Integrations and context

Agents need fresh context before they decide, and governed paths when they act. All integrations (market data, trading venues, yield providers, and Polymarket) are catalog actions on Thirdfy. Hosted runtimes reach them through the Thirdfy Agent CLI or Thirdfy MCP, not separate per-provider SDKs in EarnClaw.

Detail: Integrations at runtime. Catalog reference: Thirdfy integrations hub.

Market signals and prices

Read-only catalog actions from Allora, CoinGecko, GeckoTerminal, DeFiLlama, and related providers. Hermes and OpenClaw packs call them through the Agent CLI; Claude managed agents use MCP. These feeds inform the LLM; they do not place trades alone.

Yield intelligence

Vaults.fyi, Yield.xyz, and other earn providers in the catalog feed yield templates before allocation or rebalance intents. Same CLI and MCP rails as execution.

Trading venues

Multi-chain spot routing, Hyperliquid perps, bridges, and venue adapters are catalog actions invoked through CLI or MCP after preflight passes.

Polymarket

Prediction packs pull Polymarket Gamma and CLOB context, then place or cancel orders through governed catalog actions when setup, funding, and preflight pass.

Who it is for

Finance and crypto users

Individuals and small teams who want to earn or automate trading, yield, and onchain finance. Deploy a template, fund a wallet, and let the agent run on a schedule you control.

Builders

Developers shipping agent strategies across EVM chains and integrated venues. Use certified packs, org policies, and runtime APIs instead of rebuilding execution rails.

Operators

People who need schedules, guardrails, and audit-friendly run history. Review skips, allowance usage, and wallet state from one dashboard.

Partners

Teams embedding EarnClaw agents into existing workflows, products, or distribution. Same runtime, delegation, and observability surface for hosted deploys.

What happens at runtime

On each cycle, the runtime reads live evidence, applies template policy, and writes an execute-or-skip decision. Delegation and guardrails limit what the agent may attempt. Before any onchain action runs, policy preflight must pass.

For integrations, preflight, and runtime behavior, see Integrations at runtime. You do not need integrator docs to create your first agent.

Next

CEO beta access
How CEO holders join the EarnClaw beta, activate membership, and deploy a Hermes trading agent.
EarnClaw vision
Why EarnClaw exists, how finance agents are organized in the workspace, and how teams scale from one agent to a fleet.