Studio Platforms

Platforms define where a Studio bot can operate. They are channel surfaces for the same bot brain, knowledge, trading settings, and risk policy.

Studio is built for traders, communities, and projects that want Balchemy bots in places where crypto trading conversations already happen: Telegram groups, Discord servers, and project websites.

Platform list

Platform	Status	Use it for
Telegram	Active channel surface	DMs, groups, trading commands, community analysis, mention-based replies.
Discord	Active channel surface	Servers, channel and role policy, community trading workflows, logs.
Web Widget	Active embedded surface	Project websites, support/trading assistant widgets, visitor conversations.
X/Twitter	Limited / coming soon unless enabled for your bot	Social signal or posting workflows; do not rely on it as a primary execution channel.

Shared adapter model

Telegram and Discord use Balchemy-managed adapters. You configure behavior and policy; you do not paste raw Telegram or Discord bot tokens into Studio.

This lets Balchemy handle platform reliability, rate limits, and delivery plumbing centrally while keeping each bot's identity, knowledge, strategy, and channel permissions isolated.

What platform policy controls

Depending on the platform, configuration may include:

Owner username or guild ID.
Allowed users, channels, roles, or guilds.
Blocked users, channels, or roles.
Mention-only behavior.
Trading vs analysis permissions.
Approval settings.
Fast-buy or contract-address detection.
Partner attribution or fee-share settings.

Always start with the narrowest policy that works. For a trading-enabled community bot, avoid public/unrestricted access until you have tested the bot with small trade sizes and explicit approvals.

Use Telegram when your trading workflow happens in DMs or groups. Configure access mode, allowed usernames, mention behavior, and channel policies.

See Telegram Integration.

Discord

Use Discord when your community operates through servers, channels, and roles. Configure guild ID, allowed/blocked channels, role gates, log channel, and mention behavior.

See Discord Integration.

Use the web widget when a project wants a Balchemy bot on its own site. Configure domains, theme, quick prompts, widget identity, wallet-connect behavior, and the embed script.

See Web Widget.

The X/Twitter card may appear in Studio, but current product docs should treat it as limited or coming soon unless your UI shows it enabled for your bot. Prefer Telegram, Discord, or Web Widget for production trading workflows.

See X/Twitter.