Hub Overview
Hub is Balchemy's operations surface for 24/7 Web3 agents. Use Hub when an agent needs identity, funding, scoped MCP/API access, logs, monitoring, and ongoing operational control.
If you want to create a Telegram, Discord, or web-widget trading bot, use Studio. If you operate an always-on Web3 agent that calls Balchemy through MCP/API, use Hub.
What Hub is for
Hub helps an agent owner/operator:
- Register or onboard an agent.
- Copy and rotate agent-level MCP/API keys.
- Assign the minimum scope needed:
read,trade, ormanage. - Fund an agent wallet when the agent will trade.
- Monitor tool calls, errors, logs, and setup state.
- Verify identities used for ownership or notification flows.
- Troubleshoot agent runtime and access problems.
Hub is not a separate pricing tier and not a subscription product. It is an operating surface for agent runtime work.
Hub vs Studio
| Studio | Hub | |
|---|---|---|
| Primary actor | Trader, community operator, or project operator | 24/7 Web3 agent owner/operator |
| Primary object | Balchemy bot | Always-on Web3 agent |
| Channel model | App, Telegram, Discord, Web Widget | MCP/API runtime |
| Key model | Bot-scoped Studio MCP keys | Agent-level MCP/API keys |
| Main controls | Bot configuration, knowledge, trading cockpit, channel policy, widget | Identity, funding, scopes, logs, monitoring, key rotation |
Both surfaces use the same safety-oriented execution core. The difference is the actor, identity, and operating workflow.
Agent lifecycle
A typical Hub setup follows this path:
- Register or onboard the agent from Hub or an onboarding flow.
- Store the one-time key shown during setup.
- Fund the agent wallet if the agent will trade.
- Choose scopes for the key or token.
- Connect the MCP/API client and call
tools/list. - Monitor logs and errors from Hub.
- Rotate or revoke access when deployments or operators change.
Sensitive management actions can require owner/claim or step-up style verification. Use the UI flow rather than trying to bypass it from raw data stores.
Hub pages
| Page | Purpose |
|---|---|
| Dashboard | High-level agent operations, tool-call activity, errors, and quick navigation. |
| Agents & Keys | Registered agents and their key/setup state. |
| Agent Detail | Per-agent identity, scopes, funding, MCP config, logs, and setup controls. |
| Scopes | Explain and inspect read, trade, and manage access. |
| Logs | Review agent activity and operational events. |
| Telegram / Discord Verification | Link an operator identity for ownership, claim, or notification flows. |
The frontend redirects /hub/api-keys to /hub/agents, so key management should be treated as part of Agents & Keys and agent detail flows.
MCP/API access
Hub agents connect through scoped MCP/API access. Use the minimum scope:
| Scope | Use it for |
|---|---|
read | Status, logs, portfolio, research, and monitoring. |
trade | Trade actions allowed by policy and risk checks. |
manage | Sensitive management actions such as key rotation or configuration changes. |
Do not hand out manage access to a runtime that only needs to monitor or trade. Rotate keys when an operator or deployment changes.
Funding
An agent that trades needs funds available through its authorized agent wallet flow. Fund only the amount needed for the agent's strategy, keep unused funds out of active trading wallets, and use the Hub UI/API flow for wallet operations.
Do not edit wallet/key database collections to fund, repair, or reset an agent.
Logs and monitoring
Hub logs are the primary way to understand what an agent did and why a request failed. Use logs to inspect:
- Authentication and scope failures.
- Tool calls.
- Trading requests and policy outcomes.
- Key usage.
- Setup and verification state.
If an agent cannot call a tool, check scope first, then key status, then agent setup state.
Explorer and discovery
Explorer is the public discovery surface for verified agents and public metadata. Hub is where the agent is operated. Use Explorer to browse or share public agent profiles; use Hub to manage the agent's operational state.