> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/fees-tiers-and-staking/surge-fee-and-minimum.md).

# Surge fee and minimum

The Surge fee is **0.2% of the ADA side of every order**, reduced by your staking tier. The minimum fee is **0.978 ADA** per order.

### How it is calculated

* **Buy (ADA → token):** 0.2% of the ADA you trade.
* **Sell (token → ADA):** 0.2% of the ADA you expect to receive.
* Your staking tier reduces the base rate. See [Tiers and fee discounts](/fees-tiers-and-staking/tiers-and-discounts.md).
* Surge charges the larger of the percentage fee or 0.978 ADA.

### Why the minimum is 0.978 ADA

Cardano requires each transaction output to meet its minimum value. Surge uses **0.978 ADA** as the minimum fee so the fee output meets that requirement.

| Trade size | Percentage fee | Surge fee |
| ---------- | -------------- | --------- |
| 1,000 ADA  | 2.00 ADA       | 2.00 ADA  |
| 489 ADA    | 0.978 ADA      | 0.978 ADA |
| 100 ADA    | 0.20 ADA       | 0.978 ADA |
| 20 ADA     | 0.04 ADA       | 0.978 ADA |

The minimum applies to fee previews, required-balance panels, trade records, and analytics.

### When your rate changes

Your rate is set when you create your account. If you subscribe to staking, Surge recalculates it every six hours from your staking snapshot. A tier change applies at the next snapshot.


---

# 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.surgecardano.com/fees-tiers-and-staking/surge-fee-and-minimum.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.