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

# Vision

Collectible trading is fragmented across marketplaces, sales databases, population reports, spreadsheets, and chats. HoloScope brings that workflow into one terminal.

We started with graded Pokemon cards on Collector Crypt, then added Phygitals and Beezie, along with raw cards. Courtyard and other major collectible markets come next through the same terminal.

## What we are building

* Live listing and reprice discovery across marketplaces.
* Evidence-based valuation and deal scoring.
* Powerful search, filters, alerts, and market data.
* Simple account and wallet onboarding.
* Direct USDC trading, limit orders, bids, and sniping.
* Listing and repricing tools for sellers.
* Onchain portfolio, cost basis, and PnL tracking.
* Public trader profiles and a leaderboard.
* Referrals and $HOLO ecosystem benefits.

## Principles

**Clear.** Every signal should make sense in seconds.

**Evidence-led.** Identity and comparable sales come before price.

**Fast.** Fresh opportunities surface while they still matter.

**Controlled.** Users define permissions, limits, and automation rules.

**Onchain.** Ownership, settlement, and ecosystem activity stay verifiable.


---

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