> For the complete documentation index, see [llms.txt](https://oni.gitbook.io/oni.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oni.gitbook.io/oni.exchange/exchange/liquidity-pools.md).

# Liquidity Pools

ONI DEX facilitates decentralized trading by leveraging the power of liquidity pools, similar to the model popularized by PancakeSwap. Users can provide liquidity by depositing pairs of tokens into pools and, in return, earn a share of the trading fees generated from pool transactions, denominated in APY/APR.

**How It Works**

* Users deposit an equal value of two tokens to create a liquidity pair.
* In return for providing liquidity, participants receive liquidity provider (LP) tokens, representing their share of the pool.
* LP tokens can be staked to earn additional rewards, further enhancing the profitability of providing liquidity.

**Benefits**

* **Passive Income**: Earn trading fees and staking rewards by contributing to liquidity pools.
* **Community Contribution**: Support the ecosystem's health and stability by ensuring efficient token swaps.


---

# 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://oni.gitbook.io/oni.exchange/exchange/liquidity-pools.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.