> For the complete documentation index, see [llms.txt](https://docs.pangolin.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pangolin.exchange/pangolin-overview/introduction-to-pangolin/pangolin-v3/non-fungible-liquidity-positions.md).

# Non-Fungible Liquidity Positions

Because each liquidity position can have a custom price range and fee tier, Pangolin V3 issues **non-fungible token (NFT) representations** for LP positions instead of uniform ERC-20 pool tokens. When you add liquidity, you receive an NFT (sometimes called an LP token NFT) that represents your position’s specifics (pair, range, fee tier, and liquidity amount).\
\
Each position is unique, but it is still transferable – you can send your liquidity NFT to another address, trade it, or use it in other protocols if supported. Pangolin may offer tools or “periphery” contracts to make common positions fungible (for instance, combining identical range positions), but generally your liquidity is an individualized NFT.\
\
The use of NFTs does **NOT** affect your user experience on the Pangolin app – the interface will show your positions and allow you to manage or withdraw them normally – but it’s an important detail for integration and advanced use cases.


---

# 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.pangolin.exchange/pangolin-overview/introduction-to-pangolin/pangolin-v3/non-fungible-liquidity-positions.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.