> For the complete documentation index, see [llms.txt](https://docs.cros.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cros.world/tokenization-of-ad-assets/brand-nfts.md).

# Brand NFTs

The advertisers can also choose to create a NFT of their product or brand and launch that through the brand advertisement. Say, for example, a famous brand of sneakers, while designing an advertisement campaign for a new line of shoes, can also create a NFT collection for the same sneaker shoes.

Cros designs these brand NFT collections such that the consumer watching the advertisement can mint & buy the digital NFT of the advertised product from any of the advertisement assets across the different metaverses using an experience native to that metaverse (example, a 2-minute game quest which is an advertisement and an NFT promotion and a \*shop & mint\* interface).


---

# 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.cros.world/tokenization-of-ad-assets/brand-nfts.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.
