> 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/trust/risks-and-disclosures.md).

# Risks and Disclosures

**Market risk.** Collectibles can be volatile and illiquid.

**Data risk.** Marketplace and sales data can be delayed, incomplete, or incorrect.

**Estimate risk.** A HoloScope Estimate is market intelligence, not a guaranteed bid or resale price. Market caps and index levels are measures of the market, not money you could get by selling.

**Automation risk.** One-click buys, limit orders, alert auto-buys, sniper orders, and auto-bids can spend real USDC quickly and without asking again. Set limits you are comfortable with. An automatic order can also miss a listing or fail.

**Custody risk.** A tokenized card depends on the marketplace that stores the physical slab. Storage, insurance, and redemption are handled by that marketplace, not by HoloScope.

**Infrastructure risk.** Wallets, Solana, marketplaces, RPC providers, and HoloScope can experience delays or failures.

**Impersonation risk.** $HOLO is not live, and scammers may pretend otherwise. Trust official links only.

HoloScope provides software and information, not financial, legal, tax, or investment advice.

HoloScope is not affiliated with Nintendo, The Pokemon Company, Game Freak, or Creatures Inc.


---

# 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/trust/risks-and-disclosures.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.