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

# Aggregator Fees

#### No standard fee

Hypertrade Aggregator does not add a platform fee to your swap. There is no percentage taken from your input amount and no markup added to the route. The quote you see is built from the raw liquidity of the venues in the route.

#### Execution surplus

A swap is quoted at a minimum expected output based on current liquidity. By the time the transaction executes onchain, conditions can move in your favor, and the swap can return more than the quoted minimum. This difference is called execution surplus, also known as positive slippage.

At this stage, the protocol retains 100% of execution surplus. You always receive at least the quoted minimum output for your slippage setting. Surplus retention applies only to the upside beyond the quote, never to the quoted amount itself.

This policy funds the development and operation of the router and may change in future stages. Any change will be reflected on this page.

#### Integration fees

Apps and protocols that integrate the Aggregator API can attach their own fee to swaps routed through their integration using the fee parameter (in basis points) and `referrerAddress`. This fee is set by the integrator, not by Hypertrade, and is shown in the API response.

#### What you pay in total

* Venue fees: each DEX pool in the route charges its own swap fee (for example, 0.30% on V2-style pools). These are venue fees, not Hypertrade fees, and they are already reflected in your quote.
* Network gas: standard HyperEVM transaction costs.
* Hypertrade fee: none added to the quoted amount. Execution surplus above the quote is currently retained by the protocol.

<br>

<br>

<br>


---

# 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.ht.xyz/hypertrade-aggregator/aggregator-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.