One market summary
BTC, ETH and SOL are shown in one Telegram interface: price, change, volume and source status.
The Telegram bot collects BTC, ETH and SOL quotes from Binance and Kraken, shows price, change, volume and spread. The user sets the rules; the bot alerts on a new threshold crossing without turning into a stream of duplicate messages.
There is no need to keep several exchanges open and compare numbers manually. The bot collects data, applies the user rules and surfaces only meaningful changes.
BTC, ETH and SOL are shown in one Telegram interface: price, change, volume and source status.
The user sets a percentage and receives an alert when the movement actually crosses the threshold.
The bot shows the Binance/Kraken price difference and alerts on a meaningful spread.
Each user has their own assets, movement threshold, minimum spread and notification state.
One continuous signal is not repeated every minute: a new alert appears only after leaving the zone and crossing it again.
Quote collection and alert delivery run separately from the client bot.
The client does not need to learn terminals or charts: key metrics, rules and actions are collected in a familiar Telegram format.
Selects the required coins and gets one summary from two sources.
Sets the acceptable price movement and minimum exchange difference.
A background worker updates data regularly and stores fresh snapshots.
The message includes the asset, price, change and reason so the next decision is quick.
This architecture is useful beyond crypto: prices, stock levels, exchange rates, API metrics and any event that requires a timely notification.
Open the working bot ↗Binance and Kraken are queried in the background and compared in one workflow.
The coin list and movement/spread percentages are configurable, not hardcoded into the interface.
The user can request a fresh summary at any time without waiting for the background cycle.
An alert triggers on a zone crossing, not on every refresh of the same value.
Subscriber summary, source status and service actions are available to a separate role.
The bot receives Telegram updates over HTTPS while API monitoring runs as a separate process.
The interface stays simple while Telegram, data collection, caching and delivery are separated internally.
I will build a Telegram bot that tracks prices, stock, statuses, API metrics or other events and reports them at the right time.


