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

# Roadmap

## 1. Intelligence foundation (live)

* Scanner and reprice detection.
* HoloScope Estimates, scoring, sales, and charts.
* Liquidity, trend, population, and integrity context.
* Advanced filters and browser alerts.
* Market caps and indexes.

## 2. Trading and portfolio (live)

* Privy onboarding and embedded wallets.
* SOL deposits, automatic gas top-ups, and withdrawals.
* Direct marketplace execution.
* Inventory, positions, history, fees, and PnL.
* Cross-device profiles.
* Shareable PnL cards.

## 3. Orders and automation (live)

* Limit orders and alert auto-buys.
* Bids and auto-bids.
* HyperScope sniper orders and one-click buys.
* Spending limits and a stop switch.
* Relisting and auto-decline for sellers.
* Telegram delivery.
* Referrals.

## 4. Marketplace aggregation (in progress)

* Collector Crypt, Phygitals, and Beezie are connected.
* Raw cards are in the feed.
* Courtyard and other major collectible markets are next.
* Sealed products.
* Professional analytics and integrations.

## 5. Community (in progress)

* Public trader pages, follows, and the leaderboard are live.
* Weekly Holo Point giveaways.
* Community alert tools.

## 6. $HOLO

* Token launch.
* Holder fee tiers and order capacity.
* $HOLO priority fees on limit orders.
* Onchain flywheel reporting.


---

# 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/direction/roadmap.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.