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

# NFT Features

In order to fulfill some of the NFT mechanisms of the platform a user must have $PATIC to fulfill the functions, such as purchasing In-Game NFTs from the marketplace or alternatively minting items from in-game into NFT which require a fee in $PATIC.

Users will need $PATIC to carry out these crucial functions in game. The exact structure with the pricings will be determined closer to launch when there's more data to use to assess these aspects. However there will be a 20% fee taken on all secondary market trades and additionally all NFTs sold will be full revenue for the company.


---

# 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://projectpolyverse.gitbook.io/polyverse-token-economy-whitepaper/nft-economy/nft-features.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.