Fund and run
After deploy — your plan and credits, and the agent wallet capital, 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. Plan and credits
What it covers: your organization's plan, which adds credits every month, and the EarnOrg Credits that each running agent spends at its template's price a day.
Where to check: EarnOrg dashboard → Credits: your balance, plan, and how long your credits last.
Plans and prices: Pricing overview.
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. Execution
What it covers: onchain intents and tool-backed execution for hosted agents. It is included in the agent's price a day: there is no separate execution top-up.
Where to check: before you deploy, the wizard shows the agent's price a day and how long your credits last with it. Agent run history shows a skip when preflight blocks a cycle.
Important: EarnOrg Credits are not Thirdfy Credits from thirdfy.com/credits. See Credits and agents and Pricing FAQ.
EarnOrg wallet (your hub)
Your EarnOrg wallet is the account wallet for your signed-in user in the workspace. It is separate from each agent wallet.
| Wallet | Role |
|---|---|
| EarnOrg 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 EarnOrg or withdraw from an agent.
Typical flow:
- Add Base USDC to your EarnOrg wallet.
- Move USDC from EarnOrg into the agent wallet when you are ready to run.
- When you pull capital back, agent cash returns to your EarnOrg wallet first.
- From the EarnOrg wallet, withdraw to any external wallet you choose (your own exchange, hardware wallet, or another address you control).
Gas for Base USDC moves between EarnOrg and agents is sponsored in product, so the EarnOrg wallet does not need ETH for those transfers.
When organization security requires World ID, in-app funding waits for that proof. Withdraw does not. See World ID and organization security.
Withdrawing capital
From an agent
Cash withdraw from an agent always pays your EarnOrg 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 EarnOrg, use the EarnOrg 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 EarnOrg wallet from the agent page.
- From EarnOrg, 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 EarnOrg while a vault position is open.
From the EarnOrg wallet
Open the EarnOrg 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.