Studio Bot Cockpit
Studio is the workspace for Balchemy bots. It is designed for crypto and meme-token traders, communities, and projects that want a bot to help with trading workflows across the app, Telegram, Discord, and embedded web widgets.
Use Studio when you want to create a bot, shape its personality, add knowledge, configure trading behavior, connect community channels, embed a widget, or expose that bot through bot-scoped MCP.
Studio vs Hub
| Studio | Hub |
|---|---|
| Operates Balchemy bots | Operates 24/7 Web3 agents |
| Built for traders, communities, and project operators | Built for agent owners/operators |
| Uses bot cockpit tabs for trading, knowledge, channels, widget, and MCP | Uses agent identity, funding, scopes, logs, and agent-level MCP/API keys |
| Connects Telegram, Discord, and web widgets | Connects always-on agents through MCP/API |
If your workflow is a Telegram group, Discord server, or project website with a Balchemy bot, start in Studio. If your workflow is an always-on Web3 agent with its own identity and funding, start in Hub.
What a Studio bot controls
A Studio bot combines:
- AI personality, model behavior, response style, and guardrails.
- Knowledge base documents and Q&A.
- Trading strategy, risk, DCA, automation, approvals, and history.
- Portfolio and wallet context for active trading.
- Telegram and Discord channel configuration.
- Web widget configuration and domain controls.
- Bot-scoped MCP keys, tools, agent card, and operation logs.
Bot cockpit tabs
Each bot has its own cockpit with operational tabs.
| Tab | What it is for |
|---|---|
| Overview | Bot status, open positions, orders, and summary metrics. |
| Trading | Manual and assisted trading workflows for the bot. |
| DCA | Recurring or split-position strategy management. |
| History | Trades, approvals, status changes, and bot activity. |
| Strategy | Default order profile and named trading strategies. |
| Risk | Position, drawdown, daily loss, and execution guardrails. |
| Automation | Manual, semi-auto, or auto-submit execution behavior and pending approvals. |
| Analytics | Bot usage and activity analytics. |
| Knowledge | Uploaded docs and Q&A used for retrieval. |
| Training | Suggestions from conversation history and operator-approved refinements. |
| Platforms | Telegram, Discord, X/Twitter status, and Web Widget channel cards. |
| Widget | Embedded website widget settings, domains, preview, and script. |
| MCP | Bot-scoped MCP keys, tools, agent card, and logs. |
| Config | Personality, model, response mode, and guardrail settings. |
The cockpit header includes runtime controls such as Start, Pause, and Emergency Stop where available for the current bot state.
Platforms and community channels
Studio platform configuration is where community workflows live.
- Telegram: configure owner username, access mode, allowed users, mention behavior, and channel policies.
- Discord: configure guild, channel, role, logging, welcome, and mention behavior.
- Web Widget: embed a Balchemy bot on a project site with domains, theme, prompts, and wallet-connect settings.
- X/Twitter: appears in the platform surface, but should be treated as limited or coming soon unless the UI shows it active for your bot.
Balchemy manages the shared Telegram and Discord adapter infrastructure. You configure policy and behavior; you do not paste raw Telegram or Discord bot tokens into Studio.
Channel policies
Channel policies let you tune what a bot may do in a specific Telegram group or Discord server/channel. Depending on the platform context, policies can cover:
- Whether trading commands are accepted.
- Whether analysis-only responses are allowed.
- Whether approvals are required.
- Fast-buy or contract-address detection behavior.
- Allowed users, roles, guilds, or channels.
- Partner attribution or fee-share configuration.
Channel and widget fee-share is separate from referrals. It is a way to attribute activity to a community or integration context. Do not treat it as a guaranteed payout schedule unless the current product flow explicitly exposes that settlement path.
Web widget
The web widget is a Studio surface for projects that want a Balchemy bot on their own site. In the Widget tab you can configure:
- Allowed domains.
- Title, welcome message, position, theme, colors, and brand name.
- Quick prompts and knowledge prompt.
- Wallet-connect behavior.
- Embed script.
- Preview and status.
Use Web Widget for the dedicated setup guide.
Studio MCP
Studio MCP exposes a single Studio bot to MCP-compatible clients. It is bot-scoped: keys, tools, agent card, and logs belong to the bot cockpit.
Use Studio MCP when you want Claude, another MCP client, or an operator workflow to call a specific bot. Use Hub MCP when you are running a 24/7 Web3 agent with its own identity, funding, scopes, and logs.
Recommended setup workflow
- Create a bot from Studio.
- Open the bot cockpit and refine Config.
- Add context in Knowledge.
- Configure Strategy, Risk, and Automation if the bot trades.
- Connect Telegram, Discord, or Web Widget in Platforms and Widget.
- Set channel policies before enabling trading in any community channel.
- Create bot-scoped MCP keys only if an external MCP client needs this bot.
- Start with small trade sizes and manual or semi-auto approval before enabling broader automation.
Common issues
The bot is too active in a group. Turn on mention-only behavior and narrow channel policies.
Trading commands are ignored in Telegram or Discord. Check the channel policy. Trading must be enabled for that channel context, and the bot's trading guardrails must allow the request.
I need a website bot for another project. Use the Widget tab, configure allowed domains, and embed the generated script on the project site.
I need API keys for this bot. Use the bot cockpit MCP tab. Hub agent keys are managed from Hub → Agents & Keys and are a different surface.