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

# Designed to Grow

Finished product on ETH Blockchains and planned for 10 Blockchains in a year\
\
Supports 25 tokens in a year as per the roadmap.\
\
Miniscule marketcap of 200K\
\
\
Plus · \
\
Fully Open Source · \
\
Pinksale Audited Source Code.  \
\
Decentralized Hosting - No one can shut down the platform \
\
The benefit of holding PRVTX is that it supports 10 separate blockchains and 25 tokens; \
\
WBTC, ETHER, BNB, USDT, Cardano ADA, XRP, DOT, USDC, AVAX, Harmony ONE, Arbitrum, HECO, DAI, MoonRiver MVR, MATIC, Fantom FTM, BTCB, WETH (Polygon), JOE (AVAX), BUSD on Harmony, BUSD on Binance chain, CAKE, MANA, TRUE USD and CET allowing our users to focus on several ventures, which provides flexibility and freedom in trading.\ <br>


---

# 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://priceai.gitbook.io/priceai-whitepaper/designed-to-grow.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.