> 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/orders-and-bids.md). # Limit Orders and Bids A limit order waits for a listing at your price. A bid offers a price on a specific card, whether or not its owner has it listed. ## Limit orders Set a price and HoloScope watches new listings for you. When a match appears at or under your price, it rechecks the listing onchain and tries to buy it from your wallet. You pay only when the order fills. Each order lets you choose: * **Scope:** any copy of that card and grade, or one specific listing. * **Marketplaces:** which connected marketplaces it can buy on. * **Copies:** from 1 to 10. * **Expiry:** 1 day, 7 days, 30 days, or good until cancelled. You can edit or stop an order at any time from the Orders window in the footer. Keep enough USDC in your wallet for the fill and its fee. An order can miss a listing if another buyer gets there first. ### Open order limits An account can hold **5 open limit orders**. Once $HOLO is live, [holding it](/holoscope/ecosystem/holo-token.md) will raise that limit to as many as 50. ### Alerts that buy Attach a limit price and spend cap to an [alert](/holoscope/product/alerts.md), and matching cards are bought within those limits, even when you are away. ### $HOLO priority fee The order ticket has a priority field for $HOLO. When matching orders compete for the same listing, the order with the highest priority goes first. The plan is for this fee to be collected only when an order fills and then burned. Unfilled orders would pay nothing. **$HOLO is not live, so no priority fee is charged or burned today.** ## Bids Bids go through the marketplace's own offer system, alongside offers made anywhere else. | | Collector Crypt | Phygitals | Beezie | | --------- | --------------- | --------- | ------ | | Bids | Yes | Yes | No | | Auto-bids | Yes | No | No | When you bid, your USDC moves into the marketplace's escrow. It comes back if you cancel or the bid expires, and it pays for the card if the owner accepts. HoloScope's fee applies only when a bid fills. You choose how long a bid stays open: 1 hour, 6 hours, 1 day, 3 days, or 7 days. Collector Crypt has a $1 minimum. The Bids window in the footer shows your open bids, where you can raise or cancel them. The deal page's Offers tab shows the competition. ### Accepting an offer On your own card, each offer in the Offers tab has an **Accept** button. It opens a confirmation showing the offer, each fee by name, and what you will receive. Nothing is sent until you confirm there. One transaction from your wallet accepts it; a card listed on that marketplace is delisted in the same step. An offer HoloScope cannot accept for you links to its marketplace instead. The fees are in [Fees and referrals](/holoscope/ecosystem/fees-and-referrals.md#accepting-an-offer). ### Auto-bids An auto-bid defends your position on Collector Crypt. You set a maximum and a step: * When someone outbids you, it jumps to their price plus your step, and never above your maximum. * Past your maximum, it tells you once and leaves your bid where it is. * **Rebalance** is optional. It also brings your bid back down when the competition drops, but never below your first bid. * The bid's deadline is set once and doesn't reset when the bid moves. Each rebid cancels and replaces the offer onchain. Other bots on these markets also react within seconds, so set a maximum you are happy to pay. Bids on [live pack pulls](/holoscope/product/hyperscope.md#live-pulls) work a little differently and are covered on the HyperScope page. --- # 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/orders-and-bids.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.