> 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/intelligence/signals.md). # Understanding a Signal ## HoloScope Estimate The value supported by matching completed sales. Grader, grade, recency, market pace, and irregular trades all affect the result. ## Deal Edge How far the asking price sits below or above the estimate. ``` Deal Edge = (Estimate - Asking Price) / Estimate ``` Positive is below estimate. Negative is above estimate. ## Deal Score The overall opportunity rating. It combines edge, liquidity, confidence, identity quality, market depth, stability, and grader evidence. Deal Score ranks opportunities after risk. It is not a probability of profit. HoloScope's platform fees are accounted for, and the score is capped when evidence is thin, stale, guide-only, or from another grader. Volatility, a supported downtrend, and a very new release all lower it, while rarity or a rising trend alone never raises it. A card can show a large discount and still be a **Pass** when no resale edge survives fees or there are too few recent exits. The score doesn't guarantee net profit: other costs, listing delays, and time to sell can all change the result. ## Confidence The strength of the evidence behind the estimate. Thin, stale, mismatched, or irregular data lowers confidence. ## Graded Rarity On the detail page and in your inventory, rarity describes relative scarcity at the card's specific grade using reported population evidence. It is separate from Deal Score and does not measure price or investment quality. See [Graded Rarity](/holoscope/intelligence/graded-rarity.md) for the tiers, score, and limitations. ## Read them together A large edge can still be weak when the market is thin. A smaller edge can be stronger when the evidence and liquidity are reliable. --- # 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/intelligence/signals.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.