TradePath AI

TradePath AI is a self-reported diagnostic tool for algorithmic trading, built as a standalone C#/.NET command-line analyzer. The project analyzes structured logs from cTrader backtests to detect high-risk trade paths and explain when drawdown turns into a dangerous “tooth.” It does not currently parse raw cTrader reports or generate Pain12 records itself; it only processes pre-existing structured diagnostic data.

The author states that the tool was developed using private diagnostic instrumentation inside a cTrader cBot, with Codex and GPT-5.6 used for engineering and analysis. The public prototype is deterministic and does not call AI models during execution. It separates observation from decision-making, treating Pain12 as a diagnostic alarm rather than an automatic trigger.

Key commercial due-diligence question: Is there evidence of traction or adoption beyond the author’s own backtest?

The description states that TradePath AI is a research and developer tool, not a trading signal or financial advice provider. No revenue, customer base, or market validation are evidenced.

• The product is a standalone C#/.NET command-line analyzer.
• It reads structured PAIN12 RECOVERY DIAG records generated by private diagnostic instrumentation inside a cTrader cBot.
• It does not parse report.html, reconstruct trades from raw history, or generate Pain12 records itself.
• It analyzes:
  • Position ID
  • Trade direction and status
  • Pips and net result at Pain12
  • Worst and best movement after Pain12
  • Additional drawdown after Pain12
  • Whether the position returned to breakeven
  • Time to breakeven and worst drawdown
  • Final or current net result
• It separates records by an additional-drawdown threshold (default 6,000 pips) and reports breaches/non-breaches.
• It calculates combined NetAt12 and final results, prints detailed tables, and exports analysis to CSV.
• The tool is deterministic and does not call AI models during runtime.

• The description states that TradePath AI is an “AI-assisted diagnostic tool.”
• It claims to analyze cTrader backtests, detect high-risk trade paths, and explain when drawdown turns into a dangerous “tooth.”
• The author notes that the tool does not provide financial advice or guarantee profits.
• It is positioned as a research and developer tool, not a trading signal or automated system.
• AI was used during engineering, analysis, and documentation but not in real-time execution.

• Not evidenced. No stated target customer or ideal customer profile (ICP) is provided.
• The tool appears to be aimed at algorithmic traders or developers using cTrader.
• It is not described as a commercial product for end-users, but rather as an internal diagnostic tool used by developers.

• Not evidenced. No business model or pricing information is stated.
• The project is described as a research and developer tool, not a commercial offering.
• No indication of monetization strategy, licensing, or sales channels.

• Built with .NET, C#, algorithmic, analytics, automate, backtesting, cTrader, data, OpenAI, trading.
• Uses Codex for engineering support and GPT-5.6 for analysis and documentation.
• The tool is deterministic and does not call AI models during runtime.
• Private diagnostic instrumentation was added to an existing cTrader cBot without changing its behavior.
• Control backtest results were preserved after adding diagnostics (Net Profit: 68.83 EUR, Ending Balance: 1081.25 EUR).
• The public analyzer is a standalone executable that safely processes exported Pain12 records.

• Not evidenced. No customer data, usage metrics, or adoption indicators are provided.
• The project is described as a prototype submitted to a hackathon.
• A demonstration dataset of 13 Pain12 records was included.
• Future versions may include GUI, timelines, and AI-assisted explanations, but these are not part of the current prototype.

• Not evidenced. No competitive landscape or market positioning is described.
• The tool is focused on cTrader backtesting diagnostics.
• It does not appear to compete with existing trading platforms or tools directly; it is a diagnostic add-on for algorithmic traders.

• The tool is described as a research and developer tool, not a commercial product — this raises questions about its market readiness or scalability.
• No evidence of revenue, customers, or traction beyond the author’s own backtest.
• The project was submitted to a hackathon, suggesting it may be early-stage or experimental.
• The tool does not currently parse raw cTrader logs or generate diagnostics itself; it only processes pre-existing structured data.
• The use of AI in engineering and documentation (Codex, GPT-5.6) is noted, but not in real-time execution.

1. What is the actual commercial strategy for monetizing this tool?
2. Has it been tested or used by others beyond the author’s own backtests?
3. Are there any plans to integrate with trading platforms beyond cTrader?
4. How does the diagnostic instrumentation affect performance or execution in live trading?
5. Is there a roadmap for moving from command-line to GUI or web-based interface?
6. What is the long-term vision for this tool — is it intended as a standalone product or part of a larger suite?