Updated .
Does Hummingbot send price alerts?
Yes, on one Condor page. On 12 November 2026 that page described a routine that watches one price and sends an alert when it moves by a set percent since the previous check. Other Hummingbot pages opened that day described bot notices and an order reference price. An outside alert can also reach the bot on a broker topic.
What do the similar names mean?
On 12 November 2026 these pages used "price" for different jobs.
| Name | What the page describes |
|---|---|
| price_monitor | Percent move since the previous check |
| Telegram notices | Commands, and messages when background work finishes |
| External price source | Reference price for maker orders |
| Price band | Order ceiling and floor, unused when left at -1 |
| A level you set | Not described |
The home page calls Hummingbot an open source Python framework for strategies on any CEX and DEX, with paths for Condor and the command-line client. The price band page, as of v0.27.0, sets where orders are placed.
What does price_monitor send?
The built-in routines page lists price_monitor as a continuous routine. The connector defaults to binance, and the pair to BTC-USDT. The percent defaults to 1.0. The gap between checks defaults to 10 seconds. It tries to send a Telegram message when it starts, then checks on that gap. When the move since the previous check reaches the percent, it sends an alert. It also keeps a live report. Telegram is named for the start message only. The page does not name a channel for the move.
What does the API page describe?
The API page calls the API the central hub for running trading bots and prints v1.0.1. Market data covers candles, tickers, cross-rates, order books, and pool prices. Other parts cover accounts, order execution, bot start and stop, and an EMQX broker. It directs new users to Condor and names assistant tools for Claude, ChatGPT, and Gemini.
Its security note says the API controls live trading, and that automated scans, brute-force attempts, and misconfigured clients can lead to unauthorized trades. Basic authentication is always on. The page tells readers to use Tailscale so port 8000 stays off the public internet.
The MCP page says assistant tools can read market prices and place orders. It does not describe a standing notice at a price level. Alerts on this site are a separate connection, on assistant frameworks.
What do Condor's Telegram commands do?
The Condor Telegram page says the commands control the bot. Welcome text lists /portfolio, /bots, /trade, /agent, /keys, and /web. /trade places orders. /agent opens the assistant menu. /keys only lists exchanges. A secret is added in the Workspace, not in the chat.
Condor messages you when a delegated task completes, a routine ends, an agent sends a notification, or a restart interrupts a run. The same notices sit under the Workspace bell.
What does the broker page say?
The orchestration page describes an MQTT layer so bots on different machines share one broker. It names RabbitMQ and EMQX. Phase I, released in v1.12.0, covers start, stop, import, strategy config, and balance. Phase II is labeled released in v1.14.0, and that section says an event layer will be added for remote events over MQTT. The example is TradingView. It adds mqtt_external_events and prints no topic string.
The broker security page says a username and password are required now.
| Setting | Before | Now |
|---|---|---|
| Authentication | Anonymous connections accepted | Username and password required |
| Topics | Stock allow-all | Deny-by-default: hbot/# and hummingbot-api/response/# |
| MQTT port 1883 | 0.0.0.0 | 127.0.0.1 |
The page says port 1883 used to be reachable with no password if no restrictive firewall blocked it. Older instances have to be deployed again, because credentials are written at creation.
How can an outside alert reach the bot?
The message-bridge source subscribes to {namespace}/{instance_id}/external/event/# when external events are on. It publishes the bot's notices on {namespace}/{instance_id}/notify when the notifier is on. When commands are on, it registers start, stop, config, import, status, history, and balance.
Configuration defaults use namespace hbot, host localhost, and port 1883. External events default to on. Automatic start defaults to off. Username and password default to empty, while the security page requires both. hbot sits under the allowed hbot/# prefix.
The Hummingbot guide publishes each alert from the events feed to hbot/{instance_id}/external/event/terminal. The guide says the last segment, terminal, is the event name. The client takes the text after event/ and turns slashes into dots. On this topic, that text is the same segment.
What does the bridge leave out?
The guide says the payload is the event JSON, with the same fields the feed returned. The script does not wrap it, add an order, or call a trading API. The bot decides. The event message class has timestamp, sequence, type, and data. The guide says the listener keeps those fields and drops others.
On 12 November 2026 the home page listed signed webhooks to a server you run under built, opening later. This bridge reads the events feed and does not use a webhook. When a trading webhook fails covers that other path.
What limits apply to the key?
On 12 November 2026 the works-today list included an API for rules, alerts, receipts and the would-have-fired preview, with a key on every plan. Free includes 1,000 calls a month. Quotas lists 1 API key on Free and 1,000 included calls in a UTC month. Key steps are on API key help and the quick start.
The alert schema names price above a level, price below a level, a percent move, a volume spike, and an unusual move. World-event, funding, open-interest, and index alerts stay in the app. The events feed leaves them out.
Terminal serves the alerts you set on an events feed, with a key on every plan, and its Hummingbot guide publishes each alert, with the same fields the feed returned, to a broker you run. It is not investment advice.
FAQ
Is an external price source a price alert?
No. The external pricing page, updated as of v0.36.0, describes a reference price for maker orders: the current market, another exchange, or a custom API that returns a decimal. It does not describe a message when a price crosses a level you set.
Can Hummingbot message me when Bitcoin moves?
The routines page describes price_monitor, with default pair BTC-USDT. It sends an alert when that price moves by a set percent since the previous check. The default percent is 1.0 and the default gap is 10 seconds. That page did not describe a message at a level you set.
Does a bridged alert place an order?
No. The site guide's bridge reads the events feed and publishes each alert unchanged in its fields. It adds no order and calls no trading API. The bot decides what happens next.
Sources
Opened 2026-11-12 unless a page prints its own date. Hummingbot site footers say 11 November 2026.
- Hummingbot home: framework and the two start paths.
- Built-in routines:
price_monitor. - External price source: maker-order reference, as of v0.36.0.
- Price band: order ceiling and floor, as of v0.27.0.
- Hummingbot API: hub v1.0.1, market data, port 8000.
- Hummingbot MCP: tools for prices and orders.
- Condor Telegram: commands and notices.
- Bot orchestration: MQTT, v1.12.0, v1.14.0.
- Broker security: password, topics, port 1883.
- Message-bridge source: external-event topic and commands.
- Configuration defaults:
hbot,localhost,1883. - Event message class: four message fields.