# Metadata

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

## Metadata Structure

It is critical that your metadata adheres to the same structure as your template, which conforms to the Cardano [CIP-0025 Metadata standard](https://cips.cardano.org/cip/CIP-25). This is also the structure of the [Metadata Template](https://docs.nmkr.io/nmkr-studio/project/metadata-template) for your project. NMKR Studio is build that way that you [specify a Metadata Template](https://docs.nmkr.io/nmkr-studio/project/metadata-template) and just give the Tokens specific Values with the Metadata of the token. If you haven't specified that, please do that before continuing with the Tokens unique Metadata.

### Token specific Metadata

After you specified the [Metadata Template](https://docs.nmkr.io/nmkr-studio/project/metadata-template) you will now[ add token specific metadata](https://docs.nmkr.io/nmkr-studio/token/metadata/add-token-specific-metadata) to your Tokens to replace the [placeholders in your metadata template](https://docs.nmkr.io/nmkr-studio/project/metadata-template#placeholders-and-fields) with real values.

### Metadata for fungible Tokens

If you want to add Metadata to a fungible token that can be registered in the [Cardano Token Registry](https://github.com/cardano-foundation/cardano-token-registry) please read [this part of the documentation](https://docs.nmkr.io/nmkr-studio/token/metadata/metadata-standard-for-fungible-tokens).

### Fully on-chain NFTs

You can also use NMKR Studio to mint these[ fully on-chain NFTs by adding the file as Base64](https://docs.nmkr.io/nmkr-studio/token/metadata#fully-on-chain-nfts).<br>


---

# Agent Instructions: 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:

```
GET https://docs.nmkr.io/nmkr-studio/token/metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.