> 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/ecosystem/fees-and-referrals.md).

# Fees and Referrals

Looking is free. You pay fees only when a trade goes through.

## Terminal fee

HoloScope charges **1% on a buy** and **1% on a sell**. A bid pays the fee only if it fills. The quote shows the exact amount before you confirm.

Once $HOLO is live, [holder tiers](/holoscope/ecosystem/holo-token.md#holder-tiers) are planned to lower this fee. Holder discounts are not active yet.

## Marketplace fees

Fees charged by the connected marketplace are separate. At the time of writing:

| Marketplace     | Fee                                                                        |
| --------------- | -------------------------------------------------------------------------- |
| Collector Crypt | 2% paid by the seller                                                      |
| Phygitals       | 2% added to the buyer's price, and the seller receives the ask             |
| Beezie          | The buyer pays the ask, and Beezie's 6% fee comes out of the seller's side |

Marketplace rules can change, so go by the quote in front of you.

### Accepting an offer

Accepting an offer on your card pays the offer less that marketplace's cut: Collector Crypt's fee, Beezie's 6% fee, or nothing on a Phygitals bid. If the card is listed through HoloScope, the sale also pays HoloScope's fee. Before you confirm, HoloScope shows each fee and what you will receive.

## Deposit conversion

SOL deposits are converted to your USDC trading balance with a **0.1% fee**. USDC deposits are not converted and pay nothing. Gas top-ups and SOL withdrawals use the same 0.1% conversion.

## Network fees

Solana network fees are paid in SOL and are usually well under 0.0001 SOL per transaction. Collector Crypt pays the network fee on its own buys. Each SOL deposit keeps a little SOL for fees, and the [gas guard](/holoscope/product/deposits-and-gas.md#the-gas-guard) tops it up from your trading balance when it runs low.

Listing on Phygitals also takes a refundable deposit of about 0.0023 SOL, which comes back when the listing closes.

## Referral rewards

Each account has a unique referral link. When a new user joins through it, the referrer receives **3 Holo Points** and the new user receives **10 Holo Points**.

A referral code can also be entered once from the Profile page after signup. Referral rewards are credited once per account and cannot be self-claimed.

Referrals earn Holo Points only, not a share of trading fees.

Giveaway entry will require at least **$10 of confirmed HoloScope trading volume**, so referral-only accounts won't be able to enter a draw without trading.


---

# 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/ecosystem/fees-and-referrals.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.
