Hub Overview
Hub is Balchemy's single user-facing autonomous trading-agent product. Use Hub to create, fund, authorize, monitor, and improve an always-on Solana/Base agent through natural-language rules, scoped MCP/API access, safe runtime controls, and operational evidence.
Studio is retired as a separate bot workspace. Legacy Studio code and direct links may remain temporarily for migration or compatibility, but new product flows should start from Hub.
What Hub is for
Hub helps an agent owner/operator:
- Create or resume a Hub agent.
- Write and review natural-language rules.
- Inspect runtime mode, scheduler readiness, and degraded evidence.
- Monitor current positions, realized trades, activity, and operational logs.
- Configure Telegram/Discord Signal Sources for CA/token-signal ingestion and attribution.
- Review Revenue attribution for global swap fees, referrals, and Signal Sources where implemented.
- Copy, rotate, and revoke scoped MCP/API access.
- Connect Solana/Base wallets through authorized product flows.
Hub is not a plan, tier, subscription, or enterprise access surface. Every user receives the same standard product access. Balchemy revenue comes from the global swap-fee model on executed swaps.
Hub sections
| Section | Purpose |
|---|---|
| Dashboard | Fleet-level agent health, recent activity, errors, and quick navigation. |
| Agents | Browse, create, claim, resume, and inspect Hub agents. |
| Agent Overview | One agent's identity, claim, funding, wallets, and health state. |
| Rules | Natural-language rules, compiled summary, conflicts, and versions when available. |
| Runtime | Mode, scheduler/subscription state, pause/resume/arm/disarm affordances where authorized. |
| Positions | Current holdings, exposure, pending orders, and wallet balances. |
| Trades | Realized or pending financial actions with reconciliation state. |
| Activity | Behavioral events such as watched, held, blocked, degraded, or rule-changed. |
| Signal Sources | Telegram/Discord/source channels for CA ingestion, source health, and attribution. |
| Revenue | Global swap fees, referral attribution, source attribution, and payout status only where implemented. |
| Access | MCP/API keys, scopes, step-up, and claim-sensitive management actions. |
| Wallets | Solana/Base setup and recovery/withdrawal references through safe product flows. |
| Settings | Profile, notification, and optional advanced preferences. |
Activity, Trades, and Logs are separate. Activity explains what the agent watched or decided. Trades show financial actions and reconciliation state. Logs are operational/debug evidence.
Rules-first control
Natural-language rules are the primary control model. The web UI may show compiled summaries, conflicts, and optional advanced profile helpers, but Hub is not a mandatory form-based strategy builder.
Every applied rules or profile change should be versioned, auditable, and runtime-visible. Existing open-position exit policies must not be silently rewritten by a later settings change.
Signal Sources
Telegram and Discord in Hub are Signal Sources. They are for:
- account linking and verification,
- active groups/channels,
- CA/token-signal detection,
- allowed, blocked, and trusted submitters,
- source health,
- source attribution metadata,
- last seen signal or candidate where available.
They are not chat-bot personality, auto-response, mention-only, welcome-message, or knowledge-Q&A surfaces.
Revenue
Hub Revenue distinguishes three concepts:
- global swap fees on executed swaps,
- referral-code attribution,
- Signal Source attribution for source/channel trade origin.
Do not treat referral rewards and Signal Source fee-share as the same system. Do not promise automatic payout timing unless payout rails are implemented and verified.
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 | Trading actions allowed by policy and risk checks. |
manage | Sensitive management actions such as key rotation or configuration changes. |
The frontend redirects /hub/api-keys to /hub/agents, so key management
belongs to Agents & Keys and agent detail flows.
Funding and wallets
An agent that trades needs funds available through its authorized agent wallet flow. Fund only the amount needed for the strategy, keep unused funds out of active trading wallets, and use Hub UI/API flows for wallet operations.
Do not edit wallet/key database collections to fund, repair, or reset an agent.
Explorer and discovery
Explorer is the public discovery surface for verified agents and public metadata. Use Explorer to browse or share public agent profiles. Use Hub to operate the agent.