> 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/developer/likenft/metadata.md).

# Metadata best practice

{% hint style="warning" %}
The documentation is designed for Liker Land and LikeCoin v2. For information on [3ook.com](https://3ook.com/) and LikeCoin v3, please visit [docs.3ook.com](https://docs.3ook.com) and [dao.like.co](https://dao.like.co/).
{% endhint %}

## NFT class and instance metadata reference

No metadata standard is explicitly enforced for LikeCoin NFT. Users and dapp developers can take reference of the OpenSea standard: <https://docs.opensea.io/docs/metadata-standards>

## NFT Meta Collection for classes

In some use cases, multiple NFT classes might belong to a larger collection. i.e. classes are created and organized to form a collection, We would call these meta collections, please define these metadata fields in the related NFT classes.

| Key                               | Description                                                               |
| --------------------------------- | ------------------------------------------------------------------------- |
| nft\_meta\_collection\_id         | An ID representing a meta collection , no uniqueness is enforced on chain |
| nft\_meta\_collection\_name       | Human readable name for the meta collection                               |
| nft\_meta\_collection\_descrption | Human readable description meta collection                                |

Note that these field are merely used as a standardize and convenient way to tag classes. Chain logic does not enforce any uniqueness and validity check for these fields, so it is up to the users and develop to verify if any class tagged with a same `nft_meta_collection_id` actually belongs to any creator or collections.

## Sample

Please refer to [Writing NFT Spec](/developer/likenft/writing-nft.md)


---

# 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/developer/likenft/metadata.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.