> For the complete documentation index, see [llms.txt](https://docs.v2.like.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.v2.like.co/zh/depub/liker-land/nft-details.md).

# NFT 詳細資訊

了解你的 NFT

{% hint style="warning" %}
此文檔只適用於 Liker Land 和 LikeCoin v2。如需了解 [3ook.com](http://3ook.com/) 和 LikeCoin v3，請至 [docs.3ook.com](http://docs.3ook.com/) 及 [dao.like.co](https://dao.like.co/)。
{% endhint %}

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2FreCsyAjGXgcTQzNaMbdZ%2FBuy%20NFT%20Details.png?alt=media&amp;token=5423ed42-e3b1-488d-911b-a912db278ccf" alt=""><figcaption><p>NFT 詳細資訊</p></figcaption></figure>

1. NFT ID：每顆 NFT 獨一無二的 ID
2. 收藏者留言：在「簽署留言給創作者」步驟輸入的內容
3. 作者留言：作者在發行 NFT 時輸入的留言
4. 區塊鏈資料：展示 NFT 來源及轉手過程
5. 瀏覽內容：查看 NFT 內容
6. 檢視 NFT 系列資訊：檢視整個 NFT 系列的價格及收藏狀態

## NFT Class ID

NFT Class ID 直接是 URL 的一部份。

<figure><img src="https://887379602-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL4mdaVjNgL6A1--PV0-1995411665%2Fuploads%2Fh0UqwP0krQfoQ0DqhNlJ%2FNFT%20Class%20ID.png?alt=media&amp;token=04660659-6654-4dce-845b-beb347564b57" alt=""><figcaption><p>NFT Class ID</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.v2.like.co/zh/depub/liker-land/nft-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
