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

# Fees

### Inherited HIP-3 structure

On the Hyperliquid HIP-3 model, standard fees for a builder-deployed asset are elevated relative to validator-operated perp markets, and the deployer share is split with Hyperliquid. The published reference model:

* Standard HIP-3 asset fees are 2× the usual fees on validator-operated perp markets.
* Of the fee, 50% goes to Hyperliquid and 50% to the deployer.
* Fee tiers are volume-based, assessed on a rolling 14-day volume (evaluated daily, UTC), across taker/maker rates.

The deployer (the Force protocol) sets its portion and any promotional/reduced-fee mode within what HIP-3 permits.

### Force specifics — TBD

| Item                         | Value                                                      |
| ---------------------------- | ---------------------------------------------------------- |
| Force taker / maker schedule | TBD                                                        |
| Reduced-fee ("growth") mode  | TBD                                                        |
| Deployer share allocation    | Inherited 50/50 HIP-3 split; Force allocation TBD          |
| Interface fees               | Not applicable to the protocol; any interface sets its own |

Force fee parameters will be published here once set. As with all trading parameters, they are unset at this stage by design — see the Specification Index.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.force.xyz/perp-mechanics/fees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.