Hummingbot primary sources — 2026-05-02
Project status in this pass
- No canonical standalone whitepaper or litepaper surfaced.
- The clearest current source of truth was Hummingbot’s official website, docs portal, and main GitHub repository.
- The current first-party surface presents Hummingbot as a modular operating stack around algorithmic trading, not just a single bot binary.
Primary-source snapshots
1) Homepage / product surface
- URL: https://hummingbot.org/
- Key excerpt:
- The homepage says many individuals and institutions run Hummingbot and points users to real-time reporting for Hummingbot instance volume.
- It shows the current stack as Hummingbot API, Condor, Hummingbot Client, Gateway, Hummingbot MCP, Hummingbot Skills, and Quants Lab.
- This matters because it frames Hummingbot as a coordinated control plane for strategy deployment, operations, and AI-assisted control rather than as one standalone desktop or CLI bot.
2) Documentation overview
- URL: https://hummingbot.org/docs/
- Key excerpt:
- The docs describe Hummingbot as a community-driven, open-source Python framework for building automated market making and algorithmic trading bots.
- The docs say it is modular and extensible, allowing users to automate any trading strategy on any exchange and blockchain.
- They also split the framework into companion modules including Gateway, Dashboard/API, MCP, and Quants Lab, reinforcing that the product surface extends well beyond a single client.
3) Main GitHub README
- URL: https://raw.githubusercontent.com/hummingbot/hummingbot/master/README.md
- Key excerpt:
- The README says Hummingbot users generated over $34 billion in trading volume across 140+ unique trading venues over the past year.
- It says the mission is to “democratize high-frequency trading” by building a global community of algorithmic traders and developers around the open codebase.
- It also describes connector categories spanning centralized exchanges, onchain order books, and AMM DEXs, with Gateway covering many AMM integrations.
Working conclusion
Hummingbot is best cataloged as algorithmic-trading and market-making infrastructure with a broader exchange-connectivity and AI-control surface. The decisive evidence in this pass was the multi-repo first-party architecture: a core client, DEX middleware, centralized API, Telegram operations interface, MCP server for AI assistants, and research/backtesting tooling. The main caveat is that no single canonical whitepaper surfaced; the living docs and repo network are the real first-party source of truth.