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

# NFT

<figure><img src="/files/XVKCucKGuqo0CpXFwryx" alt=""><figcaption></figcaption></figure>

NFT has turned into an undeniable and inevitable part in Blockchain but unfortunately it has been misused in the majority of Game-Fi projects in Blockchain to the point that they have turned into a symbolic aspect of the games and are of no other use in the games than buy and sell.

NFT in Metafarmer is an extremely important part because the distinguishing feature of Non-Blockchain games from Blockchain ones is actualizing the concept of True Ownership which is only doable with the help of NFT. All valuable assets of Metafarmer are placed in the wallet of the owners as NFT, in such a way that NFTs or known as an independent tradable asset, and of course a usable one, in Metafarmer. However, the variety of uses of NFT transcends the definitions in similar projects. NFT in Metafarmer, in terms of use and essence, is divided into 5 types illustrated in the diagram down below.

<figure><img src="/files/ip2uRoSWdnKClgPhh1cO" alt=""><figcaption></figcaption></figure>


---

# 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://metafarmer.gitbook.io/metafamer-whitepaper/features/nft.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.