> 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/telegram-bot.md).

# Telegram Bot

**@holoscopetrade\_bot** brings HoloScope into Telegram: your own alerts, group deal feeds, and a browsable view of the market.

Nothing in Telegram can trade. The bot will never ask for a seed phrase, private key, password, or wallet signature. If something claiming to be HoloScope asks for one, it's a scam.

## Your alerts

Press **Connect Telegram** on your profile or the Alerts page, then press **Start** in the bot. Your [alert rules](/holoscope/product/alerts.md) now reach you as messages with the card photo, price, estimate, edge, score, and marketplace.

Each message has buttons to open the deal or the listing. You can snooze alerts for 1 hour or 8 hours, or pause them.

| Command             | What it does              |
| ------------------- | ------------------------- |
| `/status`           | Shows your connection     |
| `/alerts`           | Lists your armed alerts   |
| `/pause`, `/resume` | Stops and restarts alerts |
| `/unlink`           | Disconnects Telegram      |

## Group feeds

Add the bot to a group. It stays paused until an admin runs `/setup` and picks a feed:

* **Presets:** Best deals, Every vintage deal, or Hourly top 5.
* **Filters:** minimum score, era, grader, marketplace, set, and price.
* **Delivery:** instant, or a digest every 15 minutes, 1 hour, or 4 hours.

Anyone in the group can read the current settings with `/feed`. To stop a busy group from being flooded, instant mode posts at most 30 deals an hour, and the bot suggests a digest when more match.

## Browse the market

Anyone can use these in a direct message or a group, with or without an account:

| Command                                           | What it shows                                                        |
| ------------------------------------------------- | -------------------------------------------------------------------- |
| `/menu`                                           | The scanner's headline numbers and the best deal now                 |
| `/top`, `/vintage`, `/cheap`, `/grails`, `/fresh` | Lists of live deals                                                  |
| `/lucky`                                          | A random good deal                                                   |
| `/market`                                         | The HoloScope 500, the graded market, eras, and the sets moving most |
| `/set evolving skies`                             | A set's index, market cap, top cards, and live deals                 |
| `/scope charizard psa 9`                          | Card search with live listings and prices                            |

In a direct message, you can also just type a card name to search.

## Daily report

Send `/daily` in a linked direct message, or switch it on in a group's settings, to get the market summary once a day.


---

# 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/telegram-bot.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.