# Transaction Fees

The platform’s revenue model is designed to sustain operations and continuously serve users through diverse revenue streams. Below is a detailed breakdown of each component of the revenue model:

### Transaction Fees

Transaction fees are charged when users trade digital assets such as game items, cryptocurrencies, and NFTs on the platform. These fees support the platform’s operation by covering the cost of intermediary services, maintaining security, and facilitating seamless transactions.

* **Fee Rate:** A brokerage fee ranging from 3% to 5% of the transaction amount is applied. The specific rate depends on the type of asset and transaction size. For instance, smaller transactions involving game items might incur a higher fee, while larger cryptocurrency transactions might have a lower fee.
* **Revenue Utilization:** The fees collected contribute to the platform’s operational expenses, including server maintenance, security upgrades, and technology development. Additionally, a portion of these fees is allocated to user support services and marketing efforts. Some revenue may also be reinvested into trading events and reward programs to boost user engagement.
* **Transaction Safety:** The platform employs an escrow service to secure assets during transactions, ensuring that they are protected until the transaction is finalized. This feature enhances user confidence and underpins the importance of transaction fees as a key revenue stream.


---

# 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://tem.gitbook.io/docs/revenue-model/transaction-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.
