Kalshi-nativebotfree
Kalshi-Quant-TeleBot: what it claims, what is there, where it stops
Last checked 2026-09-08
Kalshi-Quant-TeleBot is a Python trading engine for Kalshi with a JavaScript Telegram bot in front of it. The README describes three strategies (news sentiment, statistical arbitrage between related contracts, volatility), Kelly sizing, stop-losses and a REST plus WebSocket interface server deployed on Railway.
The README calls itself enterprise-grade and marks every phase complete. Star count, activity and the absence of any published results say to read it as a well-documented skeleton.
What it does
The Python side polls Kalshi on a configurable interval (default 60 seconds), evaluates the strategies and sizes positions. The Node.js side runs a Telegram bot for commands, alerts, positions, P&L and settings changes, and a REST and WebSocket API for external monitoring.
Configuration lives in .env and src/config.py: BANKROLL 1000, MAX_POSITION_SIZE_PERCENTAGE 0.10, STOP_LOSS_PERCENTAGE 0.05, MAX_DAILY_LOSS 0.02, MAX_OPEN_POSITIONS 10, CORRELATION_LIMIT 0.7, and thresholds for each strategy.
- Python 3.8+ and Node.js 16+, 4 GB RAM minimum per the README
- KALSHI_API_KEY and KALSHI_API_BASE_URL pointed at api.elections.kalshi.com/trade-api/v2
- TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID from BotFather
Strategy
News sentiment scores articles and social posts from minus 1 to plus 1, maps them to Kalshi events by keyword, and trades when the score clears NEWS_SENTIMENT_THRESHOLD (0.6). Statistical arbitrage looks for related contracts whose prices violate a logical ordering, with the README example being a primary versus a general election, and trades the pair when the gap exceeds 5%.
Volatility trading fades extreme volatility and follows sustained moves. Position sizing is a modified Kelly. The README shows code fragments for each but publishes no backtest or live numbers.
Setup and requirements
Clone, create a venv, pip install -r requirements.txt, npm install inside telegram_ui, copy telegram_ui/.env.example to .env and fill in Kalshi and Telegram keys. The README's clone URL uses a lowercase repo name that differs from the actual repo path.
Kalshi's API requires an RSA-signed request scheme; the README's env block lists only an API key string, so check the client code before assuming auth works against the current API.
Activity and maintenance
71 stars and 23 forks as of 2026-09-08. Created 2025-12-07, last push 2026-01-09, 1 open issue. Python. Eight months without a push and no LICENSE file despite the README's MIT line. Unmaintained.
Where it falls short
The gap between the README's language and the evidence. Three strategies with sentiment models, cointegration and GARCH in a repo with 71 stars, one open issue and no results is a design document with code attached.
Kalshi only, US only, and the auth section looks out of date.
Who should use it
A developer who wants a starting layout for a Kalshi bot with a Telegram front end and is going to rewrite the strategies.
Not for capital.
Questions about Kalshi-Quant-TeleBot
Is Kalshi-Quant-TeleBot free?
The README says MIT, but the repo has no LICENSE file as of 2026-09-08.
Is Kalshi-Quant-TeleBot maintained?
No. Last push 2026-01-09.
Does Kalshi-Quant-TeleBot work with Polymarket?
No. Kalshi only.
Does Kalshi-Quant-TeleBot publish results?
No backtest or live performance numbers appear in the README.
Bots die in execution. Terminals are execution.
Wanted a bot for speed and cross-venue vision? The free Kairos terminal trades Kalshi, Polymarket and Predict.fun from one book, no keys to manage.