> For the complete documentation index, see [llms.txt](https://docs.metaproprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaproprotocol.com/developer-documentation/integration-web3-with-your-game/what-is-a-nft.md).

# What is a NFT

#### What is NFT Token:

NFT (Non-Fungible Token) is a unique digital token based on blockchain technology that represents an irreplaceable, non-interchangeable asset or item. The key characteristic of an NFT is its non-fungibility and uniqueness, meaning each token has its own distinct value and cannot be replaced or exchanged for another token in the same way as cryptocurrencies.

**Key features of NFT:**

1. **Uniqueness:** Each NFT is one-of-a-kind, distinguishing it from other tokens.
2. **Indivisibility:** NFTs cannot be divided into smaller units, unlike some other cryptocurrencies such as Bitcoin or Ethereum.
3. **Durability:** NFT data is permanently recorded on the blockchain, ensuring immutability and a public record of ownership history.
4. **Ownership:** NFT ownership is decentralized and recorded on the blockchain, eliminating the need for intermediaries and providing users with full control over their digital assets.

**NFT Token Standards:** It is also worth noting that there are different NFT token standards, with two of the most popular being ERC721 and ERC1155.

**ERC721:**

* One of the earliest NFT token standards.
* Each ERC721 token is unique, making it ideal for representing one-of-a-kind assets, such as digital art.
* Commonly used in projects related to collecting and digital art.

**ERC1155:**

* Introduces a more flexible model, allowing for the issuance of both unique and fungible tokens.
* Ideal for games where different access levels or a variety of items are needed.

The differences between these standards provide developers with various options to tailor NFTs to specific use cases.


---

# 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.metaproprotocol.com/developer-documentation/integration-web3-with-your-game/what-is-a-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.