> For the complete documentation index, see [llms.txt](https://docs.meridian.money/meridian-protocol-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meridian.money/meridian-protocol-documentation/amm/swap-fees.md). # Swap Fees **Swap Fees** In line with standard capital market practices, liquidity providers on the Meridian platform earn fees when users trade against their supplied liquidity. Fees are collected in the swapped token. For instance, in a pool of Meridian's governance token (MDN) and Move Dollar (MOD), a user swapping MOD for MDN results in liquidity providers receiving a portion of the input token, MOD. Meridian LP tokens automatically accrue these fees, representing fractional ownership of the pool. The fee structure is set by the pool creator and customizable across different asset pool types. The default swap fees are as following: * Weighted Pools: 0.15% * Concentrated Liquidity Pools: 0.03% * Stable Pools: 0.05% Protocol fees are set at 50%, with the other 50% directly accruing to liquidity providers. For example, a 1.00% fee pool would effectively allocate 0.50% of swap volume to liquidity providers and the protocol treasury, respectively --- # 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.meridian.money/meridian-protocol-documentation/amm/swap-fees.md?ask=&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.