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).
Public plan details will publish with the price table.
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. 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.
EarnClaw wallet (your hub)
Your EarnClaw wallet is the account wallet for your signed-in user in the workspace. It is separate from each agent wallet.
| Wallet | Role |
|---|---|
| EarnClaw wallet | Your hub balance. Add money here, fund agents from here, and take capital out to an external address from here. |
| Agent wallet | Capital the agent uses for its mandate (trades, vaults, margin). Each agent has its own. |
Where to find it: dashboard header / Settings (wallet card), and on agent pages when you fund from EarnClaw or withdraw from an agent.
Typical flow:
- Add Base USDC to your EarnClaw wallet.
- Move USDC from EarnClaw into the agent wallet when you are ready to run.
- When you pull capital back, agent cash returns to your EarnClaw wallet first.
- From the EarnClaw wallet, withdraw to any external wallet you choose (your own exchange, hardware wallet, or another address you control).
Gas for Base USDC moves between EarnClaw and agents is sponsored in product, so the EarnClaw wallet does not need ETH for those transfers.
Withdrawing capital
From an agent
Cash withdraw from an agent always pays your EarnClaw wallet. You cannot send agent cash straight to a custom address or to another agent. That keeps recovery on a fixed, owner-owned destination.
After the funds land in EarnClaw, use the EarnClaw wallet withdraw flow to send them onward to any wallet you want.
For yield agents, capital in a vault is not idle USDC. Full recovery is:
- Exit the vault so USDC returns to the same agent wallet.
- Withdraw that USDC to your EarnClaw wallet from the agent page.
- From EarnClaw, withdraw to your external wallet if you want the funds off-platform.
If the agent still shows an open vault position, finish the vault exit before a full cash withdraw. Liquid USDC already on the agent wallet can still be withdrawn to EarnClaw while a vault position is open.
From the EarnClaw wallet
Open the EarnClaw wallet card and withdraw USDC to the destination address you enter. This is the step where you choose any external wallet. Agent withdraw does not replace this step.
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.