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

# Inside the HoloScope Engine

The Engine turns a live listing into an inspectable market signal.

## 1. Lock the identity

HoloScope matches the card name, number, set, printing, language, year, edition, variant, grader, and grade. A price is useless when it belongs to the wrong card.

Shadowless, First Edition, reverse holo, promo stamps, and deck products stay separate. So do Traditional and Simplified Chinese printings. When a card cannot be matched safely, it does not get a price.

The same rules cover every marketplace. Each one describes its cards differently, so its listings are read into one shared identity before pricing.

## 2. Build the market lane

Completed sales are grouped by comparable identity, grader, and grade. Premium labels such as Pristine or Perfect remain separate from ordinary Grade 10 lanes.

If the exact lane lacks enough evidence, the listing is not promoted as a fully priced public opportunity.

Raw cards have their own lane, built from ungraded sales and near mint prices. A raw card never borrows a graded price.

## 3. Weight the sales

Recent sales carry more influence. Active markets update quickly; thin markets retain older evidence longer.

## 4. Check integrity

The Engine downweights isolated spikes, mismatched listings, and unusual transactions. Same-day bursts count as one date, so a single busy day cannot look like a steady market. Liquidity is measured from recent activity and sales cadence, not lifetime sale count alone.

## 5. Build the signal

The result combines:

* HoloScope Estimate;
* Deal Edge;
* Deal Score;
* Confidence;
* liquidity and trend;
* the sales ledger behind the result.


---

# 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/engine.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.