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

# Pod Fees

Each Pod is configured with the following fee types:

| Fee Type                | Description                                                          |
| ----------------------- | -------------------------------------------------------------------- |
| Wrap Fee (e.g., 0.25%)  | Charged when converting TKN → pTKN                                   |
| Unwrap Fee (e.g., 0.5%) | Charged when converting pTKN → TKN                                   |
| Cooldown (Optional)     | Users may bypass unwrap fees by waiting a predefined cooldown period |
| AMM Buy Fee             | Paid when purchasing pTKN in the paired LP                           |
| AMM Sell Fee            | Paid when selling pTKN into the paired LP                            |

All fees are routed based on a Pod-specific revenue split between LP Rewards, Partner Share and pTKN Burns.


---

# 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.peapods.finance/pods/pod-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.