Create your first agent

Step-by-step guide to the EarnClaw new-agent wizard, from framework selection through launch.

Use the New agent wizard in the EarnClaw dashboard to go from template to a deployed runtime. The walkthrough below follows the five wizard steps in order.


Before you start

  1. Sign in to EarnClaw and confirm your org is selected. See Organizations.
  2. Beta access: EarnClaw requires CEO-member eligibility during beta. See CEO beta access. Public tier thresholds publish with the price table.

Wizard walkthrough

Step 1 — Framework

Pick how the agent runs day to day. Not every template ships on every framework. The wizard only shows launchable combinations for your org. Compare frameworks in Frameworks.

Hermes

The generally available beta path for trading agents. You control the schedule, wallet, and dashboard settings while EarnClaw hosts the runtime.

OpenClaw

Soul-driven finance agents with persisted strategy artifacts and scheduled jobs.

Claude

Managed Claude sessions with MCP and policy orchestration when you do not want to host Hermes or OpenClaw directly.

On each scheduled cycle, the agent reads wallet and market 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.

Step 2 — Agent type

Choose the strategy lane available to your org. All launchable agents use wallet delegation and template guardrails. Safety checks run before execution.

See EarnClaw vision for how the three lanes fit the product.

Step 3 — Strategy

Select a reviewed template from the catalog. Each template defines:

  • Strategy profile: decision rules and venue constraints
  • Operating schedule: when the agent reviews the market
  • Run history: decisions, executed actions, and blocked actions on the agent page

Templates appear in the wizard after they pass EarnClaw launch checks. Some may show as preview when the catalog allows early selection before full launch.

See Templates for category detail and launch requirements.

Step 4 — Agent setup

Configure identity and execution prerequisites:

  • Agent name and description
  • Agent wallet — create or connect the wallet the runtime will use
  • Delegation — chain, scopes, and expiry window for what the agent may sign
  • Skills — template defaults, platform skills, or external imports (framework-dependent)
  • MCP (Claude path) — optional marketplace connections where enabled

Delegation limits what the agent may attempt even if you edit strategy copy later.

Step 5 — Guardrails and launch

Set operational policy before deploy:

  • Schedule — cron interval (template may enforce a minimum)
  • Risk caps — notional limits, slippage, daily spend where the template supports them
  • Review — confirm template, runtime, wallet, and delegation summary

Click Deploy (or Create then deploy) when preflight and billing checks pass.

See Schedules and guardrails.


After deploy

Your agent appears on the Agents list.


Troubleshooting

SymptomWhat to check
Deploy blocked (billing)Org plan deploy quota or subscription. See Pricing overview.
Delegation expiredRe-create or extend delegation in agent settings.
Preflight failedPolicy, funding, or venue readiness. Read the skip reason on the agent page.
Insufficient execution allowanceCheck Settings for your runtime plan. Upgrade the plan, reduce schedule cadence, or wait for the monthly reset. Do not buy credits at thirdfy.com/credits. See Runtime plans and execution and FAQ.
Template not in wizardTemplate may be in preview or limited rollout. Choose another template or contact support.