> For the complete documentation index, see [llms.txt](https://help.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stockcharts.com/learning-more/market-commentary/stockcharts-tv.md). # StockCharts TV StockCharts TV is the official video channel for StockCharts.com, featuring insightful, educational, and entertaining financial programming for investors and traders. The channel is devoted exclusively to charting, technical analysis education, and current market commentary from the web's top technical experts, including David Keller, CMT, Mary Ellen McGonagle, Tom Bowley, and several other prominent technical analysts. With new episodes on the channel daily and all shows available for later viewing, there's always something to watch on the official StockCharts YouTube Channel. Discover or revisit featured guest interviews, catch up on special segments, and subscribe to StockCharts on YouTube for easy access. Our shows are available on our [StockCharts TV YouTube channel](https://www.youtube.com/channel/UC-W7dUPnSvZ4oTe_8vhk-qQ). In addition to the latest uploads, you can find comprehensive playlists for each of our shows. Simply click on the video for the show you want to view. StockCharts TV shows are also organized for your convenience [on the StockCharts website.](https://stockcharts.com/tv/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.stockcharts.com/learning-more/market-commentary/stockcharts-tv.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.