> For the complete documentation index, see [llms.txt](https://docs.potionprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.potionprotocol.io/guides/nft-pricing.md).
# NFT Pricing
NFTs in Potion Protocol are priced according **Bonding Curves**.
A bonding curve is a mathematical function describing the relationship between the price and supply of an asset.
When tokens are purchased a bonding curve, each additional purchase drives the price up by an additional amount.
Likewise, selling tokens results in the price reducing along the curve.
### XY=K Curve
Currently, Potion Protocol only supports a single type of price curve: the xy=k curve.
The xy=k curve prices assets directly according to their ratio in the pool.
A pool with 10 NFTs and 10 ETH would therefore price the NFTs at 1ETH each.
Buying an NFT from the pool would raise the price to 11 ETH / 9 NFTs = 1.22222 ETH per NFT, while selling would reduce the price to 9ETH / 11 NFTs = 0.818181 ETH.
The larger the amount of liquidity in the pool, the smaller the price change will result from each buy or sell.
---
# 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.potionprotocol.io/guides/nft-pricing.md?ask=&goal=
```
`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.