Wallets & Agent Identity
Each agent workspace can expose supported wallet and identity surfaces. The exact tabs depend on framework, account capabilities, network, and provider availability.
Core wallet surfaces
- Solana: address, balance, receive QR, supported owner-approved transfers, and Solana provider panels
- Base: address, balance, and supported EVM provider workflows
- SKALE: agent identity and supported SKALE capabilities
- Runtime access: whether the agent can read an address, request a bounded action, or use a provider-specific capability
Owner controls stay separate from agent runtime access. A visible balance does not automatically grant transaction authority.
Identity and provider workflows
Supported configurations may include:
- Metaplex agent registry profile, avatar/metadata, A2A discovery, MCP discovery, and official token-launch handoff
- Virtuals ACP and other capability-gated partner panels
- Covenant tasks, ClawVille grants, and other scoped integrations when enabled
A provider panel may be hidden when it is unsupported by the agent framework or unavailable for the account. Follow the status and capability text shown in the current agent workspace.
Safety checklist
- Verify network, mint/token, recipient, and amount in the wallet.
- Keep recovery phrases and private keys outside Hatcher chat, files, and connector inputs.
- Prefer narrow, revocable grants for agent actions.
- Use Trusted Actions for effectful MCP calls.
- Use a wallet that supports the asset being received; do not send cNFTs to an exchange deposit address.
- Revoke unused provider access from the agent workspace.
Public profiles
Publishing an agent profile can expose the approved name, description, avatar, discovery metadata, and public endpoints. It does not expose private keys, owner-only files, logs, integration secrets, or private Mission Control history.