> For the complete documentation index, see [llms.txt](https://chartschool.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chartschool.stockcharts.com/table-of-contents/chart-analysis/point-and-figure-charts/p-and-f-scans-and-alerts.md).

# P\&F Scans and Alerts

## Scans and Alerts <a href="#scans_and_alerts" id="scans_and_alerts"></a>

P\&F Pattern Alerts can be found at the end of the [Predefined Scans Page](https://stockcharts.com/def/servlet/SC.scan). These are based on daily data. StockCharts.com provides daily alerts for more than 15 P\&F patterns on various exchanges.

{% hint style="info" %}
**Learn More.** [P\&F Pattern Alerts](/table-of-contents/chart-analysis/point-and-figure-charts/p-and-f-scans-and-alerts/p-and-f-pattern-alerts.md)
{% endhint %}

Chartists can also scan for specific P\&F patterns using daily data and the drop-down menu for P\&F Patterns on the [Advanced Scan Workbench](https://stockcharts.com/def/servlet/ScanUI). Over 20 P\&F patterns and criteria are included in this drop-down menu. Users can combine these P\&F patterns with other non-P\&F criteria to create genuinely unique scans.

<figure><img src="https://436553459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FERtrZrZOhufFzk6ZQO4B%2Fuploads%2FRfcSB1QASmhgGWCBMTwr%2Fpnf-userdefscan.png?alt=media&amp;token=6198b8e8-6c03-47d6-bb47-e3a41baf5295" alt="Screenshot of Scan Components in StockCharts.com"><figcaption><p>P&#x26;F user-defined scans.</p></figcaption></figure>


---

# 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://chartschool.stockcharts.com/table-of-contents/chart-analysis/point-and-figure-charts/p-and-f-scans-and-alerts.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.
