> 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/hyperscope.md). # HyperScope Good listings can go in seconds. HyperScope is the fast lane: it reads new listings straight from Solana instead of waiting on a marketplace feed, works out what each one could resell for, and lets you take it in one click. ## The board * **Flips.** Fresh listings with the resale price and net profit worked out from recent sales of that card and grade, after fees. * **Fresh, Hot, and Top ROI.** Fresh puts the newest flips first, Hot shows rising markets only, and Top ROI shows the biggest returns. You can view the board as lanes, a grid, or a table. * **Gone.** What just left the board, how fast it went, and what others took. **Missed** adds up the last hour. * **Top Loot.** The best thing on the board right now. * **Price cuts.** A listing's reprices and which way they went. Filter by marketplace, era, grader, grade, maximum price, minimum net profit, minimum return, discount to the estimate, verified sales, how often the card sells, and market trend. ## Paper and Live **Paper** simulates buys and sells without using money, so it's a good place to learn the board. **Live** spends real USDC from your wallet. Signed-in traders start in Live when it's available, and HoloScope remembers if you switch to Paper. Signed out, the board runs in Paper. ## Buying In Live, a buy button pays the price it shows. By default it takes two clicks: the first arms the button and the second buys. Turn on the one-click switch in the menu if you want to skip that step. The server refuses the buy if the listing has changed or now costs more than the button showed. ## Sniper orders A sniper order buys for you when a matching listing appears. Each one has its own name, card search, grader, maximum price, budget, and fill count. A session spend cap sits above all your orders. **Stop All** halts them at once, and it works even while the stream is reconnecting. [Limit orders](/holoscope/product/orders-and-bids.md) fill through the same engine. ## Live pulls Cards pulled from Phygitals and Collector Crypt packs and Beezie claw machines appear as they are pulled. Each one shows the marketplace's buyback offer and HoloScope's estimate when a safe one exists, and a colour tells you at a glance whether it looks worth bidding. Most pulls are bought back within seconds, so you have to be quick. You can bid only while the puller holds the card, and Beezie pulls don't take bids. * **One-tap bid:** by default, 5% above the buyback, at least 25 cents more, and never under $1. It stays open for 1 hour. * **Your own rule:** set the bid from the buyback, the estimate, or a fixed price in the HyperScope menu. * **Automatic close:** when the card leaves the puller's wallet, HoloScope closes the bid, returns your USDC, and tells you why. ## Read this first Fast buying is still real money on an illiquid market. A flip is an estimate from past sales, not a promised resale. Check the evidence for any card you don't know, and set limits you are happy to hit. --- # 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/hyperscope.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.