> For the complete documentation index, see [llms.txt](https://holoscope-trade.gitbook.io/holoscope/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://holoscope-trade.gitbook.io/holoscope/product/alerts.md).

# Alerts

HoloScope Alerts watches the market for you.

## Build a rule

Target any combination of:

* one or more sets;
* every card for a Pokemon or selected Pokemon;
* one exact card, from its Market page;
* era;
* grading company and minimum grade;
* maximum asking price;
* minimum edge or Deal Score;
* identity match or qualified deal.

Presets provide a fast starting point and remain fully editable.

## Match modes

### Instant Match

Alerts as soon as the listing identity and your filters match. Best for scarce cards where speed matters most.

### Qualified Deal

Waits for HoloScope's valuation standard and any edge or score threshold you set. Fewer alerts, stronger evidence.

## Auto-buy

An alert can also act. Attach a limit price and a spend cap, and HoloScope buys matching cards within those limits through a [limit order](/holoscope/product/orders-and-bids.md), even when you are away. Nothing buys unless you switch it on.

## Delivery

Alerts arrive in the browser, in the app's Alerts window, and in your notification bell. Link the [Telegram bot](/holoscope/product/telegram-bot.md) and they reach your phone too.

Your rules are saved in your browser. Telegram follows the rules from the browser that last opened HoloScope while signed in, so rules you make on another device may differ.


---

# 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://holoscope-trade.gitbook.io/holoscope/product/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.