Agent Wallet Management
Hub agent wallets are fund-sensitive. Use the authorized Hub UI/API flow for setup, funding visibility, trading readiness, and withdrawals where available. Do not repair, reset, or mutate wallet/key state through raw database edits.
Use this page for 24/7 Web3 agents. For Studio bot wallet workflows, use the Studio wallet and trading pages.
Studio wallets vs Hub agent wallets
| Studio | Hub | |
|---|---|---|
| Primary actor | Trader, community operator, or project operator. | 24/7 Web3 agent owner/operator. |
| Purpose | Bot trading and human-operated wallet workflows. | Agent runtime funding and trading readiness. |
| Management surface | Studio bot cockpit and wallet/trading pages. | Hub → Agents & Keys / agent detail. |
| Access model | User session and bot configuration. | Agent identity, scoped MCP/API keys, setup state, logs. |
Funding principles
- Fund only the amount intended for active trading.
- Keep staging and production funds separate.
- Confirm the target chain before sending funds.
- Keep enough native token for gas/fees where required.
- Start with small amounts before increasing automation.
- Monitor Hub logs and order history after funding.
A funded wallet does not mean every trade will execute. Trading still depends on scope, policy, risk checks, token support, slippage, provider state, and order lifecycle.
Find the agent wallet
- Open Hub → Agents & Keys.
- Select the agent.
- Open the agent detail page.
- Review setup/funding state and wallet information.
- Copy the address only from the UI/API flow you trust.
Do not copy wallet addresses from old screenshots, stale logs, or unrelated environments.
Check trading readiness
Before enabling live trading, confirm:
- The agent has a
tradekey or token. - The agent wallet is funded on the intended chain.
- Native gas token is available where required.
- Risk policy and default trade settings are intentional.
- The runtime can call
tools/listsuccessfully. - A read-only status or portfolio call works.
- Hub logs do not show setup or auth failures.
Withdrawals and sensitive wallet actions
Withdrawal or ownership-sensitive wallet actions can require manage scope plus step-up or claim-style verification. Use the Hub UI/API flow and follow the prompts shown for the specific agent.
Never:
- Export private keys from production systems.
- Paste seed phrases or private keys into prompts, support channels, logs, or screenshots.
- Edit wallet/key database collections directly.
- Reuse staging keys or wallets in production.
- Leave manage access in an unattended trading runtime.
EVM approvals
Some EVM token flows require token approvals before a sell or swap can execute. Treat approvals as fund-sensitive actions:
- Approve only the token and amount needed.
- Revoke approvals that are no longer required where the product flow supports it.
- Confirm chain and token address carefully.
- Review pre-trade and order details before execution.
Common issues
The agent cannot trade after funding. Check key scope, native gas balance, policy/risk settings, setup state, and order error details. Funding alone is not enough.
The balance looks wrong. Confirm you are viewing the correct agent, chain, and environment. Check whether the funds were sent to the exact address shown by Hub.
A withdrawal action is blocked.
The action may require manage scope, claim/ownership verification, or a fresh step-up token. Use the agent detail flow.
I lost a key. Rotate or create a new key from Hub → Agents & Keys, update the runtime, and revoke the old key if it may still exist.