Telegram bot
The bot lives at t.me/Glintcallbot. Send /start to subscribe. From that moment you get pushed every signal that crosses your threshold across all four chains.
Two types of alert
The bot pushes two streams that work independently of each other.
- Threshold alerts every new signal with score >= your /threshold. Default threshold is 60.
- Watchlist alerts every new signal for any token on your /watching list, regardless of score. Useful for following a specific token across multiple calls without lowering your global threshold.
Each stream is deduped independently. The bot will not double-push the same signal under both rules.
Command reference
/startSubscribe to threshold alerts at default 60./helpPrint the full command list./signalsShow the top 5 live signals across all chains right now./threshold 70Set your alert score floor (0-100). Default 60./watch <chain> <address>Watch a token. <chain> is base | eth | sol | hl. Watchlist alerts ignore your threshold./watch <address>Same, but the bot tries to guess the chain from the signal history./watchingList the tokens currently on your watchlist./unwatch <address>Stop watching a token./stopPause all alerts. /start again to resume.Deeplinks from the dashboard
On any token detail page on glint.fit, the TRACK IN TELEGRAM button opens the bot with a one-tap watch link. The URL embeds the chain and address:
https://t.me/Glintcallbot?start=watch_base_0xc21dd0ee...The bot parses the chain and address from that payload, registers you if you are new, and adds the token to your watchlist in one step. No typing required.
Alert format
Each push contains the token label and chain, the score with a unicode bar, the momentum and whale-flow components, the AI explanation, and quick links to the dashboard and the relevant DEX or trade venue. Watchlist alerts use the same format with a clearly different header so you know the alert fired because the token is on your list rather than because it crossed your threshold.
Polling cadence
The bot ticks every 30 seconds, looking for new signals in the last 10 minutes that you have not received yet. In practice you will see a signal 30 to 90 seconds after the engine writes it, depending on timing. VIP tier (planned) will move to a faster cadence with priority routing.