Fund and run
After deploy — runtime plan, agent wallet capital, and plan-included execution allowance before your first live cycle.
Deploying an agent is step one. Before the first live cycle, confirm three separate layers. They are easy to confuse; each pays for something different.
1. Workspace access (runtime plan)
What it covers: org runtime plan subscription: deploy quota, concurrent runtimes, LLM monthly budget, certification quota, and plan-included execution allowance per runtime.
Where to check: EarnClaw dashboard → Settings (billing / plan).
CEO capacity: Holding or locking CEO unlocks EarnClaw tiers (deploy limits, templates, operator perks). CEO is not the runtime plan and does not fund agent wallet capital. See CEO utility and Pricing FAQ.
Public tier thresholds publish with the price table. During beta, CEO-member eligibility may still apply.
2. Agent wallet capital
What it covers: funds the agent uses for its mandate (swaps, vault deposits, margin, etc.).
Where to check: Agent detail page → Wallet / funding.
| Category | Typical funding |
|---|---|
| Spot / yield on Base | USDC or strategy tokens on Base in the agent wallet |
| Perps | Venue-specific margin (e.g. Arbitrum USDC for Hyperliquid Bridge2 funding) |
| Prediction | Collateral per template requirements |
Fund the wallet before expecting live trades or deposits. Preflight will skip when balances or venue setup are insufficient.
3. Plan-included execution allowance
What it covers: onchain intents and tool-backed execution for hosted agents, up to your runtime plan monthly allowance per deployed runtime.
Where to check: Settings for the active plan. The deploy wizard shows estimated monthly usage for your schedule. Agent run history shows skips when allowance or preflight blocks a cycle.
Important: Allowance is included in the runtime plan. It is not Thirdfy Credits from thirdfy.com/credits. CEO does not replace the runtime plan. See Runtime plans and execution and Pricing FAQ.
Confirm your plan is active and the wizard estimate fits the plan before switching to live execution.
First successful cycle
Open the agent page after deploy and funding:
- Confirm runtime health and schedule are active.
- Wait for the next scheduled tick (or trigger manually if the product allows).
- In run history, look for a completed cycle with either executed intents or a documented skip with a reason code.
- Skips are normal when policy, funding, or market conditions block action. Repeated skips with the same reason usually mean a setup gap (delegation, wallet, credits).
See Observability.