> For the complete documentation index, see [llms.txt](https://docs.kyberswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyberswap.com/developer-guide/zap-as-a-service-zaas-api/fee-structure.md).

# Fee Structure

## Fees model

There are two types of fees incorporated into the Zap API:

### **Protocol Fees**

Protocol fees are charged by KyberSwap in input token for Zap In feature, and are based on 4 different token pair categories:

| Pair Category   | Protocol Fee |
| --------------- | ------------ |
| Stable pair     | 0.01%        |
| Correlated pair | 0.025%       |
| Common pair     | 0.1%         |
| Exotic pair     | 0.25%        |

* Please refer to the example file below for a list of PancakeSwap v3 pools for each of the category above. PancakeSwap v3 pools not in the list belongs to the "Exotic pair" category.

{% file src="/files/SOphu8Gyr7p0eNcB0qY4" %}
Pair category for PancakeSwap V3 pools
{% endfile %}

### **Partner Fees**

* Partner fee configuration is sent by the partner client via the API to charge a partner fee on top of the protocol fees
* Similar to protocol fees, partners will only be able to charge the fee by the input token for Zap In.
* Provides both a valid non-zero feeAddress and a positive integer feePcm (the unit is per cent mille, i.e. 1-1000th of 1%) in the API call to [GetRoute](/kyberswap-solutions/kyberswap-zap-as-a-service/kyberswap-zap-as-a-service-zaas-api/zaas-http-api.md#get-route). Otherwise, no fee will be collected for partner.


---

# 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.kyberswap.com/developer-guide/zap-as-a-service-zaas-api/fee-structure.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.