> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/terminal-sections/mini-screener.md).
# Mini screener
Aggregated metrics on the public trades of the selected market
Mini screener block showing short-window trade metrics for the selected market.
Mini screener gives a compact view of live trade metrics for the market selected in Terminal.
It mirrors the core idea of the full [Screener](/features/crypto-screener-for-hyperliquid-traders.md) tab, but focuses only on the active market so you can keep execution context visible.
## Metrics
* Number of trades.
* Percentage change.
* Volume.
* Volume delta, where negative values indicate more selling than buying during the interval.
## How to use it
Use Mini screener before submitting from the [Trade form](/terminal-sections/trade-form.md). A market with rising volume, high trade count, and strong directional delta may behave differently from a quiet market with thin activity.
For cross-market scanning, open [app.proliquid.xyz/screener](https://app.proliquid.xyz/screener).
---
# 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.proliquid.xyz/terminal-sections/mini-screener.md?ask=&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.
