> 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-status.md).

# Product Status

## Live

* Scanner across Collector Crypt, Phygitals, and Beezie, with graded slabs and raw cards.
* HoloScope Estimate, Deal Edge, Deal Score, and Confidence.
* Deal pages with sales, charts, grader comparisons, slab history, offers, and live eBay asks.
* Population data and Graded Rarity.
* Privy accounts and embedded Solana wallets.
* SOL deposits that become your trading balance, an automatic gas guard, and two-factor withdrawals.
* Direct buying and selling on all three marketplaces.
* Limit orders, including alerts that buy for you.
* Bids on Collector Crypt and Phygitals, with auto-bids on Collector Crypt.
* HyperScope: chain-read listings, one-click buys, sniper orders, and live pack pulls.
* Inventory with listing, repricing, auto-decline, and card sending.
* Portfolio, cost basis, and PnL tracking.
* Market data by set and card, market caps, and indexes including the HoloScope 500.
* Browser alerts, account notifications, and the Telegram bot.
* Public trader pages, follows, and the leaderboard.
* Holo Points and referrals.
* Public price pages and guides.

## Expanding

* Courtyard and additional marketplace connections.
* Sealed products.
* Weekly Holo Point giveaways.
* $HOLO, with holder fee tiers and priority fees. **$HOLO is not live yet.**


---

# 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-status.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.