Web Widget
The Web Widget lets a project embed a Balchemy Studio bot on its own website. It is useful for project communities that want a trading-aware assistant, support surface, or token/community bot without sending every user to the Balchemy app first.
What the widget controls
From the Studio bot Widget tab you can configure:
- Allowed domains.
- Widget title and welcome message.
- Position, size, theme, primary color, and brand name.
- Quick prompts and knowledge prompt.
- Wallet-connect behavior.
- Embed script.
- Preview and status.
The widget uses the same bot personality, knowledge, guardrails, and trading policy as the rest of the Studio bot. It is another channel for the bot, not a separate bot brain.
Setup flow
- Open the bot in Studio.
- Go to Widget.
- Add the domains where the widget is allowed to run.
- Configure title, welcome message, theme, color, position, and prompts.
- Decide whether wallet connect should be available in the widget.
- Copy the embed script.
- Install the script on the project website.
- Test the widget from the allowed domain.
Domain controls
Allowed domains prevent the widget from being embedded on arbitrary websites. Keep the allowlist narrow:
- Add production domains explicitly.
- Add staging domains only while testing.
- Remove temporary domains after launch.
If a widget fails to load, first check that the page domain exactly matches the configured allowlist.
Wallet-aware widget usage
A widget can support wallet-aware conversations where enabled. A wallet signature proves identity for the widget session; it does not give Balchemy spending authority over the user's external wallet.
Trading from a widget should still respect bot policy, channel/widget policy, scopes, and risk guardrails.
Partner attribution
A widget can carry project or partner attribution when configured. That makes it possible to analyze activity associated with an embedded project surface and, where supported by product configuration, connect that activity to fee-share metadata.
Do not treat widget attribution as a guaranteed automatic payout. Settlement details depend on the configured product flow and should be verified before making payout promises.
Widget vs Telegram/Discord
| Surface | Best for |
|---|---|
| Web Widget | Project sites, token pages, landing pages, embedded assistant experiences. |
| Telegram | Trading groups and direct chat workflows. |
| Discord | Server, role, and channel-based communities. |
Use the widget when users are already on a project website. Use Telegram or Discord when the community conversation already happens in chat.
Common issues
The widget does not appear. Check allowed domains and confirm the embed script is installed on the same domain.
The widget appears but cannot answer project-specific questions. Add project docs or Q&A to the bot Knowledge tab and test again.
Wallet connect does not show. Confirm the wallet-connect option is enabled for the widget and that the browser wallet is available.
Widget trading should be restricted. Use bot risk settings and channel/widget policy. Do not rely on the embed alone as a safety boundary.