diff --git a/single-page/Quantconnect-Cloud-Platform.html b/single-page/Quantconnect-Cloud-Platform.html index c771a78b22..cc3da0aeeb 100644 --- a/single-page/Quantconnect-Cloud-Platform.html +++ b/single-page/Quantconnect-Cloud-Platform.html @@ -142,94 +142,111 @@

Table of Content

  • 11.4 Strategies
  • 11.5 Deployment
  • 11.6 Results
  • -
  • 12 Object Store
  • -
  • 13 Community
  • -
  • 13.1 Code of Conduct
  • -
  • 13.2 Forum
  • -
  • 13.3 Discord
  • -
  • 13.4 Profile
  • -
  • 13.5 Academic Grants
  • -
  • 13.6 Integration Partners
  • -
  • 13.7 Affiliates
  • -
  • 13.8 Research
  • -
  • 13.9 Strategies
  • -
  • 14 API Reference
  • -
  • 14.1 Authentication
  • -
  • 14.2 Project Management
  • -
  • 14.2.1 Create Project
  • -
  • 14.2.2 Read Project
  • -
  • 14.2.3 Update Project
  • -
  • 14.2.4 Delete Project
  • -
  • 14.2.5 Collaboration
  • -
  • 14.2.5.1 Create Project Collaborator
  • -
  • 14.2.5.2 Read Project Collaborators
  • -
  • 14.2.5.3 Update Project Collaborator
  • -
  • 14.2.5.4 Delete Project Collaborator
  • -
  • 14.2.5.5 Lock Project
  • -
  • 14.2.6 Nodes
  • -
  • 14.2.6.1 Read Project Nodes
  • -
  • 14.2.6.2 Update Project Nodes
  • -
  • 14.3 File Management
  • -
  • 14.3.1 Create File
  • -
  • 14.3.2 Read File
  • -
  • 14.3.3 Update File
  • -
  • 14.3.4 Delete File
  • -
  • 14.4 Compiling Code
  • -
  • 14.4.1 Create Compilation Job
  • -
  • 14.4.2 Read Compilation Result
  • -
  • 14.5 Backtest Management
  • -
  • 14.5.1 Create Backtest
  • -
  • 14.5.2 Read Backtest
  • -
  • 14.5.2.1 Backtest Statistics
  • -
  • 14.5.2.2 Charts
  • -
  • 14.5.2.3 Orders
  • -
  • 14.5.2.4 Insights
  • -
  • 14.5.3 Update Backtest
  • -
  • 14.5.4 Delete Backtest
  • -
  • 14.5.5 List Backtests
  • -
  • 14.6 Live Management
  • -
  • 14.6.1 Create Live Algorithm
  • -
  • 14.6.2 Read Live Algorithm
  • -
  • 14.6.2.1 Live Algorithm Statistics
  • -
  • 14.6.2.2 Charts
  • -
  • 14.6.2.3 Portfolio State
  • -
  • 14.6.2.4 Orders
  • -
  • 14.6.2.5 Insights
  • -
  • 14.6.2.6 Logs
  • -
  • 14.6.3 Update Live Algorithm
  • -
  • 14.6.3.1 Liquidate Live Portfolio
  • -
  • 14.6.3.2 Stop Live Algorithm
  • -
  • 14.6.4 List Live Algorithms
  • -
  • 14.6.5 Live Commands
  • -
  • 14.6.5.1 Create Live Command
  • -
  • 14.6.5.2 Broadcast Live Command
  • -
  • 14.7 Optimization Management
  • -
  • 14.7.1 Create Optimization
  • -
  • 14.7.2 Read Optimization
  • -
  • 14.7.3 Update Optimization
  • -
  • 14.7.4 Delete Optimization
  • -
  • 14.7.5 Abort Optimization
  • -
  • 14.7.6 List Optimization
  • -
  • 14.7.7 Estimate Optimization Cost
  • -
  • 14.8 Object Store Management
  • -
  • 14.8.1 Upload Object Store Files
  • -
  • 14.8.2 Get Object Store Metadata
  • -
  • 14.8.3 Get Object Store File
  • -
  • 14.8.4 Delete Object Store File
  • -
  • 14.8.5 List Object Store Files
  • -
  • 14.9 AI Assistance
  • -
  • 14.9.1 Tools
  • -
  • 14.9.1.1 Backtest Initialization
  • -
  • 14.9.1.2 Code Completion
  • -
  • 14.9.1.3 Error Enhancement
  • -
  • 14.9.1.4 PEP8 Conversion
  • -
  • 14.9.1.5 Syntax Check
  • -
  • 14.9.1.6 Search
  • -
  • 14.10 Reports
  • -
  • 14.10.1 Backtest Report
  • -
  • 14.11 Account
  • -
  • 14.12 Lean Version
  • -
  • 14.13 Examples
  • +
  • 12 Research Pipeline
  • +
  • 13 Object Store
  • +
  • 14 Community
  • +
  • 14.1 Code of Conduct
  • +
  • 14.2 Forum
  • +
  • 14.3 Discord
  • +
  • 14.4 Profile
  • +
  • 14.5 Academic Grants
  • +
  • 14.6 Integration Partners
  • +
  • 14.7 Affiliates
  • +
  • 14.8 Research
  • +
  • 14.9 Strategies
  • +
  • 15 API Reference
  • +
  • 15.1 Authentication
  • +
  • 15.2 Project Management
  • +
  • 15.2.1 Create Project
  • +
  • 15.2.2 Read Project
  • +
  • 15.2.3 Update Project
  • +
  • 15.2.4 Delete Project
  • +
  • 15.2.5 Collaboration
  • +
  • 15.2.5.1 Create Project Collaborator
  • +
  • 15.2.5.2 Read Project Collaborators
  • +
  • 15.2.5.3 Update Project Collaborator
  • +
  • 15.2.5.4 Delete Project Collaborator
  • +
  • 15.2.5.5 Lock Project
  • +
  • 15.2.6 Nodes
  • +
  • 15.2.6.1 Read Project Nodes
  • +
  • 15.2.6.2 Update Project Nodes
  • +
  • 15.3 File Management
  • +
  • 15.3.1 Create File
  • +
  • 15.3.2 Read File
  • +
  • 15.3.3 Update File
  • +
  • 15.3.4 Delete File
  • +
  • 15.4 Compiling Code
  • +
  • 15.4.1 Create Compilation Job
  • +
  • 15.4.2 Read Compilation Result
  • +
  • 15.5 Backtest Management
  • +
  • 15.5.1 Create Backtest
  • +
  • 15.5.2 Read Backtest
  • +
  • 15.5.2.1 Backtest Statistics
  • +
  • 15.5.2.2 Charts
  • +
  • 15.5.2.3 Orders
  • +
  • 15.5.2.4 Insights
  • +
  • 15.5.3 Update Backtest
  • +
  • 15.5.4 Delete Backtest
  • +
  • 15.5.5 List Backtests
  • +
  • 15.6 Live Management
  • +
  • 15.6.1 Create Live Algorithm
  • +
  • 15.6.2 Read Live Algorithm
  • +
  • 15.6.2.1 Live Algorithm Statistics
  • +
  • 15.6.2.2 Charts
  • +
  • 15.6.2.3 Portfolio State
  • +
  • 15.6.2.4 Orders
  • +
  • 15.6.2.5 Insights
  • +
  • 15.6.2.6 Logs
  • +
  • 15.6.3 Update Live Algorithm
  • +
  • 15.6.3.1 Liquidate Live Portfolio
  • +
  • 15.6.3.2 Stop Live Algorithm
  • +
  • 15.6.4 List Live Algorithms
  • +
  • 15.6.5 Live Commands
  • +
  • 15.6.5.1 Create Live Command
  • +
  • 15.6.5.2 Broadcast Live Command
  • +
  • 15.7 Optimization Management
  • +
  • 15.7.1 Create Optimization
  • +
  • 15.7.2 Read Optimization
  • +
  • 15.7.3 Update Optimization
  • +
  • 15.7.4 Delete Optimization
  • +
  • 15.7.5 Abort Optimization
  • +
  • 15.7.6 List Optimization
  • +
  • 15.7.7 Estimate Optimization Cost
  • +
  • 15.8 Object Store Management
  • +
  • 15.8.1 Upload Object Store Files
  • +
  • 15.8.2 Get Object Store Metadata
  • +
  • 15.8.3 Get Object Store File
  • +
  • 15.8.4 Delete Object Store File
  • +
  • 15.8.5 List Object Store Files
  • +
  • 15.9 AI Assistance
  • +
  • 15.9.1 Tools
  • +
  • 15.9.1.1 Backtest Initialization
  • +
  • 15.9.1.2 Code Completion
  • +
  • 15.9.1.3 Error Enhancement
  • +
  • 15.9.1.4 PEP8 Conversion
  • +
  • 15.9.1.5 Syntax Check
  • +
  • 15.9.1.6 Search
  • +
  • 15.10 Reports
  • +
  • 15.10.1 Backtest Report
  • +
  • 15.11 Account
  • +
  • 15.12 Lean Version
  • +
  • 15.13 Agent Management
  • +
  • 15.13.1 Agents
  • +
  • 15.13.2 Tasks
  • +
  • 15.13.2.1 Create Task
  • +
  • 15.13.2.2 Read Task
  • +
  • 15.13.2.3 Update Task
  • +
  • 15.13.2.4 Delete Task
  • +
  • 15.13.2.5 List Tasks
  • +
  • 15.13.3 Deployments
  • +
  • 15.13.3.1 Create Deployment
  • +
  • 15.13.3.2 Read Deployment
  • +
  • 15.13.3.3 Update Deployment
  • +
  • 15.13.3.4 List Deployments
  • +
  • 15.13.3.5 Stop Deployment
  • +
  • 15.13.3.6 Delete Deployment
  • +
  • 15.13.3.7 Read Conversation
  • +
  • 15.14 Examples
  •  

    @@ -565,7 +582,11 @@

    Physical access to our servers is limited to a few dedicated team members whom QuantConnect has vetted. Only those credentialed team members can access the physical servers, and we schedule all work in advance. - Work on the servers is always done in pairs to prevent single rogue actors from accessing the servers. We host our servers in a world-class security facility (Equinix) with security staff 24/7. + Work on the servers is always done in pairs to prevent single rogue actors from accessing the servers. We host our servers in a world-class security facility, on co-located servers racked in + + Equinix + + , with security staff 24/7.

    Information and Digital Security @@ -1481,7 +1502,11 @@

    Live Trading Nodes

    - Live trading nodes enable you to deploy live algorithms to our professionally-managed, co-located servers. + Live trading nodes enable you to deploy live algorithms to our professionally-managed, co-located servers racked in + + Equinix + + . You need a live trading node for each algorithm that you deploy to our co-located servers. Several models of live trading nodes are available. More powerful live trading nodes allow you to run algorithms with larger universes and give you @@ -1639,6 +1664,133 @@

    Live Trading Nodes

    +

    Assistant Nodes

    + + +

    + Assistant nodes enable you to deploy assistant tasks. + The more assistant nodes your organization has, the more concurrent assistant tasks that you can run. + More powerful assistant nodes have more cores and RAM to handle larger, more demanding tasks. + The following table shows the specifications of the assistant node models: +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + Name + + Number of Cores + + RAM (GB) + + Agents +
    + A-MICRO + + 1 + + 1 + + 1 +
    + A1-1 + + 1 + + 1 + + 1 +
    + A4-8 + + 4 + + 8 + + 4 +
    + A16-32 + + 16 + + 32 + + 16 +
    + +

    + Refer to the + + Pricing + + page to see the price of each assistant node model. + Your first organization includes one free A-MICRO assistant node, which is capped at 100,000 tokens per month. + The token cap is lifted and the node is replaced when you + + upgrade your organization to a paid tier + + and + + add a new assistant node + + . +

    +

    + To view the status of all of your organization's nodes, see the + + Resources panel + + of the IDE. + When you launch an assistant task, it uses the best-performing resource by default, but you can + + select a specific resource to use + + . +

    + + +

    Sharing Resources

    @@ -3036,7 +3188,7 @@

    Introduction

    There are three tiers of support seats and each tier provides different services. You can file support tickets to get private assistance with issues, but support tickets should not replace your efforts of performing your own research and reading through the documentation. If you need further assistance than what our Support Team offers, consider hiring an - + Integration Partner . @@ -3059,11 +3211,11 @@

    email , - + Discord , or the - + forum . We will review your submission. If we confirm you've found a bug, we will create a GitHub Issue to have it resolved. Subscribe to the GitHub Issue to track our progress in fixing the bug. @@ -3156,8 +3308,8 @@

    For more information on this feature, see - - Strategy Development + + AI Assistance .

    @@ -3470,7 +3622,7 @@

    LEAN CLI , and the - + QuantConnect REST API , which includes installation and subjects that don't apply to the Cloud Platform. @@ -4052,7 +4204,7 @@

    Ticket Quotas

    Chat with - + Mia for immediate assistance. We trained it on hundreds of algorithms and thousands of documentation pages to provide contextual assistance for most issues you may encounter when developing a strategy. @@ -5801,7 +5953,7 @@

    Giving to Others

    To show your appreciation for contributions in the forum, - + give some QuantConnect Credit (QCC) rewards . The following table shows the available QCC rewards: @@ -7020,7 +7172,7 @@

    Backtesting
    - + Sharing Backtests
    @@ -9333,6 +9485,87 @@

    +

    Order Tagging

    + + +

    + You can add + + tags + + to your orders to track why each trade was placed. This is useful for debugging your algorithm's trading logic because you can include the indicator values or conditions that triggered the order. +

    +
    +
    public class OrderTaggingAlgorithm : QCAlgorithm
    +{
    +    private ExponentialMovingAverage _emaShort;
    +    private ExponentialMovingAverage _emaLong;
    +    private Symbol _symbol;
    +
    +    public override void Initialize()
    +    {
    +        SetStartDate(2024, 9, 1);
    +        SetEndDate(2024, 12, 31);
    +        SetCash(100000);
    +
    +        _symbol = AddEquity("SPY", Resolution.Daily).Symbol;
    +        _emaShort = EMA(_symbol, 10);
    +        _emaLong = EMA(_symbol, 30);
    +    }
    +
    +    public override void OnData(Slice data)
    +    {
    +        if (!_emaShort.IsReady || !_emaLong.IsReady) return;
    +
    +        if (_emaShort > _emaLong && !Portfolio[_symbol].IsLong)
    +        {
    +            MarketOrder(_symbol, 100, tag: $"BUY: ema-short: {_emaShort:F4} > ema-long: {_emaLong:F4}");
    +        }
    +        else if (_emaShort < _emaLong && !Portfolio[_symbol].IsShort)
    +        {
    +            MarketOrder(_symbol, -100, tag: $"SELL: ema-short: {_emaShort:F4} < ema-long: {_emaLong:F4}");
    +        }
    +    }
    +}
    +
    class OrderTaggingAlgorithm(QCAlgorithm):
    +    def initialize(self) -> None:
    +        self.set_start_date(2024, 9, 1)
    +        self.set_end_date(2024, 12, 31)
    +        self.set_cash(100000)
    +
    +        self._symbol = self.add_equity("SPY", Resolution.DAILY).symbol
    +        self._ema_short = self.ema(self._symbol, 10)
    +        self._ema_long = self.ema(self._symbol, 30)
    +
    +    def on_data(self, data: Slice) -> None:
    +        if not self._ema_short.is_ready or not self._ema_long.is_ready:
    +            return
    +
    +        ema_short = self._ema_short.current.value
    +        ema_long = self._ema_long.current.value
    +        if ema_short > ema_long and not self.portfolio[self._symbol].is_long:
    +            self.market_order(self._symbol, 100, tag=f'BUY: ema-short: {ema_short:.4f} > ema-long: {ema_long:.4f}')
    +        elif ema_short < ema_long and not self.portfolio[self._symbol].is_short:
    +            self.market_order(self._symbol, -100, tag=f'SELL: ema-short: {ema_short:.4f} < ema-long: {ema_long:.4f}')
    +
    +

    + The tag is saved to the + + result files + + that you can download for local analysis. Unlike + + logging statements + + , order tags are attached directly to each order, so you don't need to search through logs to match a message to a specific trade, and they don't consume your + + log quota + + . +

    + + +

    Charting

    @@ -9370,7 +9603,7 @@

    Object Store

    The Object Store is a key-value data store for low-latency information storage and retrieval. - During a backtest, you can build large objects you’d like to analyze and write them for later analysis. + During a backtest, you can build large objects you'd like to analyze and write them for later analysis. This workflow can be helpful when the objects are large and plotting is impossible or when you want to perform analysis across many backtests.

    @@ -10592,8 +10825,10 @@

    Example

    bbdf[['price', 'lowerband', 'middleband', 'upperband']].plot();
    -
    #load "../QuantConnect.csx"
    -using QuantConnect;
    +   
    #load "../QuantConnect.csx"
    +
    +
    +
    using QuantConnect;
     using QuantConnect.Data;
     using QuantConnect.Algorithm;
     using QuantConnect.Research;
    @@ -11735,11 +11970,11 @@ 

    Share Backtests

    To attach the embedded backtest result to a forum discussion, see - + Create Discussions or - + Post Comments . @@ -14174,7 +14409,7 @@

    method or the - + /backtests/orders/read endpoint. @@ -14391,11 +14626,11 @@

    Share Results

    To attach the embedded backtest result to a forum discussion, see - + Create Discussions or - + Post Comments . @@ -18483,7 +18718,11 @@

    Delivery

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. @@ -18665,7 +18904,11 @@

    Delivery

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. @@ -18813,142 +19056,150 @@

    Delivery

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. -

    -

    - Live data takes time to travel from the source to your algorithm. - The QuantConnect latencies vary depending on the data provider, but for US Equities, we have a latency of 5-40 milliseconds. - A much more significant source of latency is the round trip order times from brokers, which can vary from 100ms to 5 seconds. - QuantConnect is not intended for high-frequency trading, but we have integrations to high-speed brokers if you need. -

    - - - -

    Historical Data

    - - -

    - When you - - request historical data - - or run - - warm-up + Most live trading algorithms run on co-located servers racked in + + Equinix - , the amount of historical data you can access depends on the resolution of your data subscriptions. The following table shows the amount of trailing historical data you can access for each data resolution: -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    - Resolution - - Available History -
    - Daily - - All historical data -
    - Hour - - All historical data -
    - Minute - - 1 year -
    - Second - - 2 months -
    - Tick - - 1 month -
    - - - -

    Pricing

    - - -

    - The QuantConnect data provider serves Crypto Futures data for free. -

    - - - -

     

    - -
    -
    -

    QuantConnect

    -

    CFD

    -
    -
    -

    Introduction

    - - -

    - The QuantConnect data provider provides a stream of CFD trades and quotes to your trading algorithm during live execution. Live data enables you to make real-time trades and update the value of the securities in your portfolio. -

    - - - -

    Sourcing

    - - -

    - The QuantConnect data provider consolidates CFD market data from OANDA. -

    - - - -

    Bar Building

    - - -

    - We aggregate ticks to build bars. -

    -

    - In live trading, bars are built using the exchange timestamps with microsecond accuracy. This microsecond-by-microsecond processing - of the ticks can mean that the individual bars between live trading and backtesting can have slightly different ticks. As a result, it's possible for a - tick to be counted in different bars between backtesting and live trading, which can lead to bars having slightly different open, high, low, close, and volume values. -

    - - - -

    Delivery

    - - -

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. +

    +

    + Live data takes time to travel from the source to your algorithm. + The QuantConnect latencies vary depending on the data provider, but for US Equities, we have a latency of 5-40 milliseconds. + A much more significant source of latency is the round trip order times from brokers, which can vary from 100ms to 5 seconds. + QuantConnect is not intended for high-frequency trading, but we have integrations to high-speed brokers if you need. +

    + + + +

    Historical Data

    + + +

    + When you + + request historical data + + or run + + warm-up + + , the amount of historical data you can access depends on the resolution of your data subscriptions. The following table shows the amount of trailing historical data you can access for each data resolution: +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    + Resolution + + Available History +
    + Daily + + All historical data +
    + Hour + + All historical data +
    + Minute + + 1 year +
    + Second + + 2 months +
    + Tick + + 1 month +
    + + + +

    Pricing

    + + +

    + The QuantConnect data provider serves Crypto Futures data for free. +

    + + + +

     

    + +
    +
    +

    QuantConnect

    +

    CFD

    +
    +
    +

    Introduction

    + + +

    + The QuantConnect data provider provides a stream of CFD trades and quotes to your trading algorithm during live execution. Live data enables you to make real-time trades and update the value of the securities in your portfolio. +

    + + + +

    Sourcing

    + + +

    + The QuantConnect data provider consolidates CFD market data from OANDA. +

    + + + +

    Bar Building

    + + +

    + We aggregate ticks to build bars. +

    +

    + In live trading, bars are built using the exchange timestamps with microsecond accuracy. This microsecond-by-microsecond processing + of the ticks can mean that the individual bars between live trading and backtesting can have slightly different ticks. As a result, it's possible for a + tick to be counted in different bars between backtesting and live trading, which can lead to bars having slightly different open, high, low, close, and volume values. +

    + + + +

    Delivery

    + + +

    + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. @@ -19083,7 +19334,11 @@

    Delivery

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. @@ -19249,7 +19504,11 @@

    Delivery

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. @@ -19389,7 +19648,11 @@

    Delivery

    , include a live stream. In these cases, we deliver the data as a live stream to your algorithm.

    - Most live trading algorithms run on co-located servers racked in Equinix. Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters. + Most live trading algorithms run on co-located servers racked in + + Equinix + + . Co-location reduces several factors that can interfere with your algorithm, including downtime from internet outages, equipment repairs, and natural disasters.

    Live data takes time to travel from the source to your algorithm. The latency of the alternative data depends on the specific dataset you're using. @@ -20415,7 +20678,7 @@

    Hybrid Data Provider

    When you - + deploy a live algorithm with the Charles Schwab brokerage , you can use a third-party data provider, the Charles Schwab data provider, or both. @@ -21666,7 +21929,11 @@

    Introduction

    - A live algorithm is an algorithm that trades in real-time with real market data. QuantConnect enables you to run your algorithms in live mode with real-time market data. Deploy your algorithms using QuantConnect because our infrastructure is battle-tested. The algorithms that our members create are run on co-located servers and the trading infrastructure is maintained at all times by our team of engineers. It's common for members to achieve 6-months of uptime with no interruptions. + A live algorithm is an algorithm that trades in real-time with real market data. QuantConnect enables you to run your algorithms in live mode with real-time market data. Deploy your algorithms using QuantConnect because our infrastructure is battle-tested. The algorithms that our members create are run on co-located servers racked in + + Equinix + + and the trading infrastructure is maintained at all times by our team of engineers. It's common for members to achieve 6-months of uptime with no interruptions.

    @@ -23531,6 +23798,110 @@

    +

    FIX Integration

    + + +

    + FIX (Financial Information eXchange) integration lets existing Interactive Brokers (IB) clients route orders from QuantConnect through their IB account. If you already hold an IB account, you can subscribe to QuantConnect directly from the IB Client Portal to enable FIX order routing. +

    +

    + Before you start, make sure you have an active IB account and access to the IB Client Portal. +

    +

    + Follow these steps to add FIX support to your IB account: +

    +
      +
    1. + Log in to the + + IB Client Portal + + , open + + Settings + + , click + + Research Subscriptions + + , open + + News & Research Subscriptions + + , and then click + + Manage Subscriptions + + . +
    2. +
    3. + Select + + QuantConnect + + from the list of subscriptions to create the FIX session, and then click + + Continue + + . +
    4. +
    5. + On the + + Review Your Research Subscriptions + + screen, review the market-data agreements and disclosures, and then confirm to proceed. +
    6. +
    7. + On the + + Service Account Configuration + + screen, click the + + Configure + + gear next to QuantConnect. +
    8. +
    9. + In the + + Service Account Configuration for QuantConnect + + dialog, select the IB account(s) you want to link, enter your QuantConnect user name in the + + Quantconnect Username + + field, and then click + + Save + + . +
    10. +

      + The user name you enter is the default subscriber for the QuantConnect service. You can select multiple accounts here. When you later connect from QuantConnect to IB, you enter this same user name to authenticate. +

      +
    11. + Back on the + + Service Account Configuration + + screen, click + + Continue + + . +
    12. +
    13. + Acknowledge and confirm the OMS Riders and Addendum. +
    14. +

      + After you confirm, your subscription is complete and the selected information is added to the FIX connection for order validation. +

      +
    + + +

    Asset Classes

    @@ -24801,6 +25172,141 @@

    Deploy Live Algorithms

    +

    Deploy Live Algorithms FIX

    + + +

    + You must have an available + + live trading node + + for each live trading algorithm you deploy. +

    +

    + Follow these steps to deploy a live algorithm: +

    +
      +
    1. + + Open the project + + you want to deploy. +
    2. +
    3. + Click the + Lightning icon + + Deploy Live + + icon. +
    4. +
    5. + On the Deploy Live page, click the + + Brokerage + + field and then click + + + Interactive Brokers + + + from the drop-down menu. +
    6. +
    7. + Enter your + + IB + + user name (see + + FIX Integration + + ). +
    8. +
    9. + Click the + + Node + + field and then click the live trading node that you want to use from the drop-down menu. +
    10. +
    11. + + (Optional) + + In the + + Data Provider + + section, click + + Show + + and change the data provider or add additional providers. +
    12. +

      + In most cases, we suggest using + + both the QC and IB data providers + + . +

      +

      + If you use + + IB + + data provider and trade with a paper trading account, you need to share the market data subscription with your paper trading account. For instructions on sharing market data subscription, see + + Account Types + + . +

      +
    13. + + (Optional) + + + Set up notifications + + . +
    14. +
    15. + Configure the + + Automatically restart algorithm + + setting. +
    16. +

      + By enabling + + automatic restarts + + , the algorithm will use best efforts to restart the algorithm if it fails due to a runtime error. This can help improve the algorithm's resilience to temporary outages such as a brokerage API disconnection. +

      +
    17. + Click + + Deploy + + . +
    18. +
    19. + If your IB account has 2FA enabled, tap the notification on your IB Key device and then enter your pin. +
    20. +
    +

    + The deployment process can take up to 5 minutes. When the algorithm deploys, the + + live results page + + displays. If you know your brokerage positions before you deployed, you can verify they have been loaded properly by checking your equity value in the runtime statistics, your cashbook holdings, and your position holdings. +

    + + +

    Troubleshooting

    @@ -27962,6 +28468,15 @@

    +

    Rate Limit

    + + +

    + Charles Schwab limits order requests (place, update, and cancel) to 120 requests per minute and 4,000 order requests per day. To avoid hitting these limits, design your algorithm to issue orders sparingly. +

    + + +

    Fees

    @@ -38460,7 +38975,11 @@

    Introduction

    - Deploy your trading algorithms live to receive real-time market data and submit orders on our co-located servers. As your algorithms run, you can view their performance in the Algorithm Lab. Since the algorithms run in QuantConnect Cloud, you can close the IDE without interrupting the execution of your algorithms. Deploying your algorithms to live trading through QuantConnect is cheaper than purchasing server space, setting up data feeds, and maintaining the software on your own. To deploy your algorithms on QuantConnect, you just need to follow the + Deploy your trading algorithms live to receive real-time market data and submit orders on our co-located servers racked in + + Equinix + + . As your algorithms run, you can view their performance in the Algorithm Lab. Since the algorithms run in QuantConnect Cloud, you can close the IDE without interrupting the execution of your algorithms. Deploying your algorithms to live trading through QuantConnect is cheaper than purchasing server space, setting up data feeds, and maintaining the software on your own. To deploy your algorithms on QuantConnect, you just need to follow the Deploy Live Algorithms @@ -38477,7 +38996,11 @@

    Resources

    - Live trading nodes enable you to deploy live algorithms to our professionally-managed, co-located servers. + Live trading nodes enable you to deploy live algorithms to our professionally-managed, co-located servers racked in + + Equinix + + . You need a live trading node for each algorithm that you deploy to our co-located servers. Several models of live trading nodes are available. More powerful live trading nodes allow you to run algorithms with larger universes and give you @@ -39293,7 +39816,7 @@


    Collection of insights emitted since the last notification. See - + Insight for the schema of each object. @@ -39311,7 +39834,7 @@


    Collection of order events since the last notification. For the conceptual model, see - + OrderEvent in the API Reference . The webhook serialization differs from the API response. See the Order Event Schema table below for the webhook-specific schema. @@ -40577,16 +41100,16 @@

    To programmatically analyze orders, call the - + - ReadBacktestOrders + ReadLiveOrders read_live_orders method or the - + /live/orders/read endpoint. @@ -41195,6 +41718,13 @@

    Introduction

    If your algorithm is perfectly reconciled, it has an exact overlap between its live and OOS backtest equity curves. Deviations mean that the performance of your algorithm has differed between the two execution modes. Several factors can contribute to the deviations.

    +

    + To generate the OOS reconciliation curve for a live deployment and overlay live vs. backtest equity and order fills from the Research Environment, see + + Live Reconciliation + + . +

    @@ -43674,9 +44204,414 @@

     

    - +
    +

    Research Pipeline

    + +
    +
    +

    Introduction

    + + +

    + The Research Pipeline is a kanban board that enables you to easily monitor the state of your organization. + Think of it as a structured approach to bringing your ideas through the stages of research validation, backtesting, paper trading, and ending with live trading. + Each card represents one project in QuantConnect Cloud. + Simply add projects to the board, then drag-and-drop them, to move them throughout the various stages of the pipeline as your team completes tasks. + To view the board, + + log in to the Algorithm Lab + + and then click the + + Research Pipeline + + tab. +

    + Research Pipeline kanban board with cards across Ideas, Research, Backtest, Paper Trading, and Live Trading lists. +

    + To supercharge your productivity, add some + + AI assistants + + to your Research Pipeline. + We offer a set of highly-skilled AI assistants that you can add to your organization. + They are each pre-configured to specialize in a particular phase of the Research Pipeline, but you can always define custom assistants to fit your organization's needs. +

    + + + +

    Stage 0: Ideas

    + + +

    + The + + Ideas + + list on the Research Pipeline should contain cards that describe new trading ideas for your team's researchers to explore. + To add ideas to the list, click the + + + Add card + + icon in the top-right corner of the list, enter a description of the trading idea, and then click + + Save + + . +

    +

    + If you need some help generating some trading ideas, an + + Ideas Assistant + + can add a steady stream of novel trading ideas to your organization's + + Ideas + + list. + This assistant analyzes recent financial news articles and trading blog posts. + It then adds a card to the list with a concise description of the strategy, including the underlying logic, the types of assets it would trade, and any specific indicators or datasets it would utilize. +

    + + + +

    Stage 1: Research

    + + +

    + The + + Research + + list on the Research Pipeline should contain a card for each project that your research team is currently investigating. + During the research stage, the goal is to perform preliminary analysis to assess the viability of the trading idea before committing resources to a formal backtest. + This stage helps filter out weak ideas early, refine hypotheses, and identify potential pitfalls. +

    +

    + To add cards to the + + Research + + list, drag-and-drop a card from the + + Ideas + + list. + Alternatively, click the + + + Add card + + icon in the top-right corner of the list, enter a description of the trading idea, and then click + + Save + + . +

    +

    + If you need some help researching ideas, add + + Research + + and + + Research Validation Assistants + + to your organization. + The Research Assistant has access to tools that let it write, read, and execute research notebooks, and it produces a research report in the project that documents its process and findings — typically covering empirical evidence, statistical significance, and a deep analysis of the fundamental reason for the edge of the trading idea. +

    +

    + The Research Validation Assistant then pressure-tests that work, using the same notebook tools to check the model's residuals for stationarity, serial correlation, heteroscedasticity, and stability between training and testing windows. + Together, they decide whether an idea has earned its place in the backtesting queue or whether it should be sent back before any engineering time is spent on it. +

    + + + +

    Stage 2: Backtest

    + + +

    + The + + Backtest + + list on the Research Pipeline should contain a card for each project that your backtest team is currently investigating. + During the backtest stage, the goal is to implement the trading idea in an error-free, event-driven algorithm. + This stage helps filter out strategies that passed the research phase but have poor performance after running a backtest with realistic + + reality modeling + + . +

    +

    + To add cards to the + + Backtest + + list, drag-and-drop a card from the + + Ideas + + or + + Research + + lists. + Alternatively, click the + + + Add card + + icon in the top-right corner of the list, enter a description of the trading idea, and then click + + Save + + . +

    +

    + If you need some help backtesting ideas, add a + + Backtest Assistant + + to your organization. + This assistant has access to tools that enable it to write algorithms, fix coding errors, run backtests, interpret backtest results, and optimize parameters. + The output of this assistant is an algorithm that's proven to underperform the market or an algorithm that's ready for testing in the paper trading environment. +

    + + + +

    Stage 3: Paper Trading

    + + +

    + The + + Paper Trading + + list on the Research Pipeline should contain a card for each project that your team is currently running live with the + + paper trading brokerage + + . + During the paper trading stage, the goal is to confirm the strategy works as expected in a live environment and diagnose any deviations. +

    +

    + To add cards to the + + Paper Trading + + list, drag-and-drop a card from the + + Backtest + + list. +

    +

    + If you need some help validating ideas with paper trading, add a + + Paper Testing Assistant + + to your organization. + This assistant has access to tools to deploy algorithms, analyze their live performance, and adjust the algorithm logic if necessary. + As it runs, it verifies the following questions: +

    + +

    + When any of these questions fail validation, the assistant reviews the code, debugs the algorithm, edits the logic, and redeploys the project. + If the assistant determines the strategy is not ready for live trading with real money, it stops the algorithm and sends you a report. +

    + + + +

    Stage 4: Live Trading

    + + +

    + The + + Live Trading + + list on the Research Pipeline should contain a card for each project that your organization is running live with real money. + During this final stage, the goal is to ensure the algorithm continues running and to intervene when necessary. + To add cards to the + + Live Trading + + list, drag-and-drop a card from the + + Paper Trading + + list. +

    +

    + If you need some help monitoring your live algorithms, add a + + Live Monitoring Assistant + + to your organization. + This assistant has access to tools to deploy algorithms, read their current positions, and scan for material news events that affect the positions. + As it runs, it assesses the directional risk of your holdings given breaking news events. + When it detects an event that can significantly reduce the value of your holdings, it notifies you so you can act. +

    + + + +

    Project Archive

    + + +

    + The + + Archived Items + + section at the bottom of the Research Pipeline should contain a card for each project to which you're no longer allocating resources. + These may be ideas that failed the research validation stage, strategies that underperformed in the backtesting stage, or algorithms that lost their edge in live trading. +

    +

    + To add projects to the archive, drag-and-drop a card from one of the stages of the Research Pipeline. + You can always recover projects from the archive later on. +

    + + + +

    Update Cards

    + + +

    + Follow these steps to update the title or body of a card on the Research Pipeline: +

    +
      +
    1. + Click on a card. +

      + The + + Card + + tab shows the current title and description. +

      + Card tab showing the current title and description. +
    2. +
    3. + Click + + Edit Idea + + . +
    4. +
    5. + Enter the new title and description. +
    6. +
    7. + Click + + Save + + . +
    8. +
    + + + +

    View Deployments

    + + +

    + When you assign a card to an Assistant and the Assistant is currently working on the task, the card displays “Running”. +

    + Card on the Research Pipeline displaying the Running status. +

    + To view the deployment details, click + + Running + + . + The deployment view page displays the output of the Assistant(s) assigned to the task. +

    + Deployment view showing the output of the Assistants assigned to the task. +

    + To open the project associated with the task, click the project link at the top of the deployment view. +

    +

    + To interrupt the assistant during its run, in the top-right corner of the deployment view, click the + + + stop + + icon. +

    +

    + To view all the current and historical tasks, follow these steps: +

    +
      +
    1. + Log in to the + + Algorithm Lab + + . +
    2. +
    3. + In the left navigation bar, click + + Organization > Assistants + + . +
    4. +
    5. + Click the + + Tasks + + tab. +
    6. +
    + Tasks tab on the Assistants page showing current and historical tasks. +

    + From this view, you can click the + + Status + + column to open the deployment view of the task or click + + Delete + + to remove the task from the view. +

    + + + +

    Quotas

    + + +

    + Assistants have a fair-use quota, but are essentially uncapped. + The number of agents you can concurrently run in your organization and the amount of tokens you can use depends on your team's + + Assistant Nodes + + . +

    + + + +

     

    + +
    +

    Object Store

    @@ -44039,7 +44974,7 @@

    Usage by Project

     

    -
    +

    Community

    @@ -44055,7 +44990,7 @@

    Community