Every message BetLLM can send you
There are six message types below, from an early heads-up to live in-game alerts — including the message that fires when there's no bet to make at all. Nothing here is hidden behind a paywall — this is the full list.
1 · Early preview
Sent a few minutes before the model's official checkpoint (around the 17, 24 and 31-minute marks), this is a heads-up, not a final call — it shows what the model is currently leaning toward so you aren't caught off guard when the real signal lands a few minutes later. The official decision at the next checkpoint can differ from the preview if the game state changes.
2 · Live signal tracked
The core signal. At a live checkpoint, if the model's probability for one side clears the statistical edge required against the bookmaker's own price, this message fires with the pick, the price it was taken at, and the model's calibrated probability — logged immediately so the call can never be edited after the fact.
3 · NO_BET / declined
This is the message people usually don't expect from a "betting bot" — and it's the one the project treats as non-negotiable. When there's no live bookmaker price yet, the model isn't confident enough, or the edge isn't statistically proven, BetLLM says so explicitly instead of guessing. A decline is a correct outcome, not a missed opportunity.
4 · Main portfolio signal
A separate, broader portfolio that tracks the model's single best favorite per match rather than every live checkpoint — useful if you want fewer, higher-conviction notifications instead of a message at every checkpoint.
5 · Odds-spike alert
Bookmaker prices move live during a map. If the price on a map BetLLM is already watching suddenly jumps well above what the model's probability would justify, this alert flags it — independent of whether a bet was already tracked.
6 · Aegis pickup
Dota-specific and not a betting signal at all: the moment either team picks up Roshan's Aegis, this fires immediately so you have the same real-time game-state information the model itself reacts to on the next checkpoint.