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

# Fees

Paragon follows the HIP-3 fee structure on Hyperliquid. All fees are transparent with no hidden costs.

## Trading Fees

Paragon markets follow Hyperliquid's standard fee schedule. Fees are charged per trade based on whether you add or remove liquidity (maker vs taker), with reduced rates for high-volume traders.

→ [Hyperliquid Fee Schedule](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees)

## Fee Distribution

Under HIP-3, trading fees are split between the protocol and the underlying infrastructure.

| Recipient        | Share |
| ---------------- | ----- |
| Paragon Protocol | 50%   |
| Hyperliquid      | 50%   |

## Funding Rates

Perpetual futures use funding rates to keep prices aligned with the underlying index. Funding is exchanged between long and short positions at regular intervals.

| Condition                       | Who pays         |
| ------------------------------- | ---------------- |
| Positive funding (perp > index) | Longs pay shorts |
| Negative funding (perp < index) | Shorts pay longs |

Each market sets a **funding multiplier** that scales its funding rate — values below 1 dampen funding relative to the raw basis. Per-market values are listed in the [market specifications](/resources/specifications.md#market-specifications); the underlying funding mechanism follows Hyperliquid's.

For equities, the multiplier is set so perpetual carry tracks how the underlying is financed in traditional markets — nearer to short-term benchmark rates such as SOFR plus a modest spread than to crypto's higher baseline. It also softens funding during weekends and off-hours, when the underlying is not trading.

Each market also sets a **funding clamp**: the band, in 8-hour terms, that bounds how far funding can move away from the average premium toward the interest-rate component. While the premium sits inside the band, funding is the interest-rate component alone, so a wider clamp keeps funding from reacting to basis narrower than the bid-ask spread. Per-market clamp values are listed in the [market specifications](/resources/specifications.md#market-specifications).

Current funding rates are displayed on the trading interface.

→ [Hyperliquid Funding Rates](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/funding)

## No Hidden Fees

| Fee Type            | Cost |
| ------------------- | ---- |
| Deposits            | Free |
| Withdrawals         | Free |
| Account maintenance | Free |
| Inactivity          | Free |

The only costs are trading fees and funding rate payments.


---

# 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://docs.paragon.trade/trading/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.