Trading Brokers Supported by LumiBot¶

There are several different brokers that you can use to trade with Lumibot, and we’re adding more as we speak! Learn more about how they work and how to set them up here.

Conceptual illustration: strategy logic connected to a broker trade ticket

Common LumiBot broker paths¶
Broker path	Main asset classes	Authentication	Setup
Alpaca	Stocks, ETFs, options, crypto	API keys or OAuth	Alpaca guide
Charles Schwab	Equities, ETFs, single-leg options	OAuth application	Schwab guide
Interactive Brokers REST	Multi-asset markets supported by the account	Client Portal session	IBKR REST guide
Interactive Brokers legacy	Multi-asset markets supported by TWS	TWS or IB Gateway	Legacy IBKR guide
CCXT exchanges	Crypto spot, margin, or derivatives by exchange	Exchange API keys	CCXT comparison
Bitunix	USDT perpetual futures	API key and secret	Bitunix guide
Tradier	Stocks and options	Access token and account number	Tradier guide

Broker setup is easier on BotSpot because the broker connection, strategy runtime, account checks, monitoring, alerts, audit history, and kill-switch controls live in one platform.

Connect brokers through the website. Avoid rebuilding secret storage, environment variables, broker account checks, and deployment configuration for every server.
Start from backtested code. Move the same Lumibot strategy from hosted backtesting to paper or live trading without rebuilding the infrastructure around it.
Monitor what the bot is doing. Review logs, trades, account state, alerts, and decisions in one place so you can understand why a strategy acted.
Use AI and MCP with broker context. BotSpot can work from the web app, your phone, Telegram, Discord, Claude, ChatGPT, Codex, Cursor, and other MCP clients while keeping the broker and strategy context together.

Try connecting a broker and deploying a sample Lumibot strategy on BotSpot

Lumibot broker and data source integrations

Contents: