> For the complete documentation index, see [llms.txt](https://support.moonshot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.moonshot.com/trade/leverage/fees.md).

# Fees

When you trade with leverage, you pay two types of fees. The **transaction fee** is a flat charge each time you open or close a position. The **borrowing fee** accrues over time based on the amount you’ve borrowed. Together, they make up the total cost of trading with leverage.

### Transaction fees

| Trade size | Fee                        |
| ---------- | -------------------------- |
| $5-$100    | 0.20% with a $0.25 minimum |
| >$100      | 0.10%                      |

{% hint style="info" %}
Fees subject to change - see [Terms](https://moonshot.com/terms) for more
{% endhint %}

### Leverage fees 

When you open a leveraged position, you’re borrowing from a liquidity pool to increase your exposure. That borrowing comes with a cost: **borrowing fees,** designed to reward liquidity providers for supplying assets and to keep the system healthy as traders take on leverage.\
\
Instead of long vs. short funding payments, as some exchanges do, we use a straightforward borrow-fee model. Borrowing fees compound hourly based on the amount you’ve borrowed, and may change over time based on market conditions. \
\
These are outstanding fees that are accumulated over the total time your position is open, and are paid the next time you modify or close your position. If unpaid fees get too close to your position's value, your position will be liquidated to cover them. 


---

# 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://support.moonshot.com/trade/leverage/fees.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.