# Fees

### Fees

PredictBase is fully decentralized and transparent — and so is the fee model. Here’s a full breakdown of fees you may encounter while using the platform.

***

#### Trading Fee (2% )

Each trade (buy/sell) includes a **2% transaction fee**, which is split evenly:

| Fee Type             | Amount | Description                                                              |
| -------------------- | ------ | ------------------------------------------------------------------------ |
| **Creator Revenue**  | 1%     | Paid to the market creator after the market is resolved                  |
| **Protocol Revenue** | 1%     | Used to fund PredictBase development, infrastructure & **PREDI** buyback |

**These fees are included in your quoted share price.**

**Example:**\
You want to buy **$100 USDC worth of shares** in the Lakers market:

* **$1 USDC** goes to **creator revenue**
* **$1 USDC** goes to the **platform**
* **You will receive shares worth the remaining $98 USDC, and the seller will receive $98 USDC.**

***

#### How is **Protocol Revenue used**?

* Supporting platform development and future improvements
* **25% of protocol revenue** is allocated for **quarterly PREDI buyback and burn**, helping reduce supply and support token value

***

#### No Hidden Costs

* No monthly fees
* No deposit or withdrawal fees

***

***

For more on earnings, visit [Creating a Market ](/docs/using-predictbase/creating-a-market.md)or [Claiming Winnings](/docs/using-predictbase/claiming-winnings.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://predictbase.gitbook.io/docs/resources/fees.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.