Agent Operator Guide
Hub is for operating 24/7 Web3 agents, not for a separate product tier or generic control panel.
Use this guide when you own or operate an agent that needs Balchemy identity, funding, scoped MCP/API access, logs, and monitoring.
Operator responsibilities
A Hub agent operator is responsible for:
- Registering or onboarding the agent.
- Storing the one-time MCP/API key securely.
- Funding the agent only with capital intended for active trading.
- Choosing minimum scopes for each runtime.
- Watching logs and tool-call errors.
- Rotating or revoking keys when access changes.
- Keeping production and staging secrets separate.
Agent detail controls
Open Hub → Agents & Keys → [Your Agent] for per-agent controls such as:
- MCP endpoint and key state.
- Read/trade/manage scope configuration.
- Funding and setup status.
- Agent wallet information.
- Activity logs.
- Claim or ownership-sensitive actions where available.
Do not use raw database edits for wallet, key, or audit operations.
Safe operating pattern
- Start with
readscope to verify connectivity. - Call
tools/listand confirm the visible capabilities. - Add
tradeonly for the runtime that should place orders. - Keep
manageout of unattended runtimes unless absolutely required. - Monitor Hub logs after each deployment.
- Rotate keys after every production secret or operator change.