> For the complete documentation index, see [llms.txt](https://en-docs.mintway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en-docs.mintway.io/the-company/.-business-background/3.-problems-in-the-nft-market/b.-item-type.md).

# B. ITEM Type

NFT is not a finished market, but a starting stage. The structure of the business model is very simple, and the focus is on a distributed ledger that proves ownership of digital assets rather than special technologies, and thus images that can be easily implemented digitally is occupies most of item.

Currently, through NFT, various business projects such as collectible games, sports stars' cards, and images that give artistic value have been created and sold at high prices, but so far the focus is on works and game items rather than digital assets.

Therefore, the current NFT business model does not deviate significantly from the transaction concept using images such as games, collections, sports, metaverse, and art, 3D models, and videos, and does not present the value of actual digital assets and it hasn't presented a completely different new type of item yet.


---

# 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://en-docs.mintway.io/the-company/.-business-background/3.-problems-in-the-nft-market/b.-item-type.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.
