> For the complete documentation index, see [llms.txt](https://docs.polymarketradar.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polymarketradar.xyz/overview.md).

# Overview

<figure><img src="/files/oMXL1Vxb6jUWdldUNo5U" alt=""><figcaption></figcaption></figure>

#### What is PolyRadar

PolyRadar is an anomaly detection and analytics platform for Polymarket. It helps users discover unusual trader activity, monitor wallets, analyze signals, and act faster through a Telegram-native workflow.

***

#### Why PolyRadar

PolyRadar is built for users who want more than raw trade feeds. It turns market activity into structured signals, trader insights, and actionable alerts.

#### Core value

* Detect unusual activity across Polymarket
* Follow traders and wallets in real time
* Analyze trader behavior with PolyRadar AI
* Trade directly from Telegram
* Access anomaly alerts via API

***

#### Legal / Risk Notice

A short section:

* informational and analytical use
* not investment advice
* users remain responsible for trading decisions
* market data and signal interpretation may change over time


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.polymarketradar.xyz/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.