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

# HoloScope

HoloScope is the trading terminal and aggregation layer for onchain collectibles. It is not a marketplace.

HoloScope reads listings from Collector Crypt, Phygitals, and Beezie, matches each one to completed sales, and turns the evidence into a clear estimate, edge, score, and confidence rating. From one terminal you can inspect the market, buy, bid, set limit orders, snipe fresh listings, list your own cards, and track your portfolio, while every order settles through the marketplace that holds the card.

Graded slabs are the core of the market, and raw cards are in the feed too. Courtyard is next.

## How it works

1. HoloScope detects a new or repriced listing.
2. The Engine locks the card identity and matching grader lane.
3. Sales, liquidity, recency, and market quality are evaluated.
4. The result becomes a readable signal with supporting evidence.
5. You buy, bid, set an order, or save an alert for the next one.
6. Positions, inventory, and PnL stay visible from your profile.

## Start here

* [Product Status](/holoscope/product-status.md)
* [Scanner and Intelligence](/holoscope/product/platform.md)
* [The Deal Page](/holoscope/product/deal-page.md)
* [Trading Terminal](/holoscope/product/trading-terminal.md)
* [HyperScope](/holoscope/product/hyperscope.md)
* [Market and Indexes](/holoscope/product/market.md)
* [Inside the HoloScope Engine](/holoscope/intelligence/engine.md)
* [Roadmap](/holoscope/direction/roadmap.md)


---

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