> For the complete documentation index, see [llms.txt](https://docs.algoboxpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algoboxpro.com/fundamentals/120-day-program.md).
# 120 Day Program
Overview Of The AlgoBox™ 120 Day Program
The AlgoBox™ 120 Day Program is structured as a comprehensive guide to help you learn the AlgoBox™ tools, indicators, strategies, methodologies, and tactics.
The program is divided into three 40-day periods, each with its own specific focus and purpose.
AlgoBox™ 120 Day Program.
For optimal results, consistently follow the program for the full 120 days without interruption.
No matter how busy you are, you can still make progress. Adjust the 40-day cycle to fit your learning schedule.
***
## Video Tutorials: 120 Day Program
{% embed url="" %}
WATCH: This short video quickly explains the 120 Day Program.
{% endembed %}
## 1st 40 Days
{% embed url="" %}
WATCH: Vinny E. Mini welcomes you to your first 40 Days of learning.
{% endembed %}
## 2nd 40 Days
{% embed url="" %}
WATCH: Vinny E. Mini ushers you to your second 40 Days of practice.
{% endembed %}
## Final 40 Days
{% embed url="" %}
WATCH: Vinny E. Mini teaches you about your final 40 Days of training.
{% endembed %}
***
Only available on AlgoBox™ for NinjaTrader 8. [Try AlgoBox™ for free today.](https://www.algoboxpro.com/start-trial)
[Disclaimer](/links/disclaimer.md)
---
# 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://docs.algoboxpro.com/fundamentals/120-day-program.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.
