> 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/product/market.md). # Market and Indexes The Market tab zooms out from single deals to the whole graded Pokemon market. ## Sets and cards Browse every set and sort by release order, market cap, set value, top gainers, or top declines. Then open a set to see its cards. A card's page shows its near mint price, graded sales by grade, population, market cap, and live listings across marketplaces. It also shows how much each grade is worth compared with the raw card. You can set an alert for that exact card from there. ## Market cap ``` Graded market cap = reported graded copies x sale-backed price for that grade ``` Only sale-backed prices count, so a grade with no sales adds no value. When a population report is shared across versions of the same card, it counts once. A market cap is a way to compare size, not money you could actually get for those cards. Most copies are not for sale, and selling a lot of them would move the price. ## Indexes Indexes follow the market caps of a group of cards over time, so the cards that matter most move the number most: * **HoloScope 500:** the top 500 cards. You can see which are closest to joining or leaving. * **Graded market:** the graded market as a whole. * **Eras and sets:** each era and set on its own. Each index has a chart, its member cards and their weights, and a heatmap showing what is pulling it up or down. ## Public price pages You don't need an account to look up a card. [Public price pages](https://holoscope.trade/pokemon-card-prices) cover sets and cards, and the [guides](https://holoscope.trade/guides) explain tokenized cards, buying onchain, and how the marketplaces differ. --- # 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/product/market.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.