> For the complete documentation index, see [llms.txt](https://docs.vapordex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapordex.io/vapordex/vape-token/genesis/market-valuation.md).
# Market Valuation
Finally, the **market valuation** is determined by the community when it sets the initial price of $VAPE. This occurs when the first liquidity pool is created by the community. The market valuation is determined by pairing x-amount of VAPE tokens with y-amount of a 2nd token. The resulting calculation is \[Total Value of 2nd Token] / \[Quantity of VAPE Tokens paired].
As an example, if the individual who creates the first liquidity pool determines that VAPE should be worth $0.1547 and they want to create the pool with 100 VAPE tokens, they would need to add 15.47 USDC worth of value for the 2nd token in the pair. The creation of the liquidity pool is a mechanic that ensures that there isn’t a runaway or unrealistic valuation.
The above graphic shows a variety of hypothetical scenarios, showing what the market price, market cap, and fully diluted value of VAPE would be — based on how much value is paired with VAPE when the first liquidity pool is initially created.
---
# 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.vapordex.io/vapordex/vape-token/genesis/market-valuation.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.
