> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/toolkits/weekly-profiles-tm/scanner.md).

# Scanner

ICT Weekly Profiles Scanner

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-42cfc2d212626adee72b1467a08d0c82fa8e8330%2Fdocs-wp-005.png?alt=media" alt=""><figcaption></figcaption></figure>

The ICT Weekly Profiles tool offers a comprehensive scanner designed to enhance trading insights by providing the following profile types:

* Former Profile
* Predicted Profile
* Actual Profile
* Future Profile

**Former Profile**

This represents the detected profile from the previous week, offering a clear reference point for analyzing past market behavior and identifying recurring patterns.

**Predicted Profile**

A collection of profiles generated through advanced weekly profile detection algorithms, giving traders a forward-looking perspective to anticipate potential market movements.

**Actual Profile**

This is the real-time representation of the current weekly profile, allowing traders to monitor market activity as it unfolds.

**Future Profile**

Leveraging the Markov Chain statistical method, this profile projects future market behavior, offering traders a probabilistic outlook to guide strategic planning.

By combining historical, predictive, real-time, and statistical insights, the ICT Weekly Profiles scanner serves as a powerful tool for comprehensive market analysis and improved trading decisions.


---

# 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.candelacharts.com/toolkits/weekly-profiles-tm/scanner.md?ask=<question>&goal=<user_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.
