> For the complete documentation index, see [llms.txt](https://docs.nemus.earth/nemus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nemus.earth/nemus-docs/nemus-litepaper/the-nemus-nft/artwork.md).

# Artwork

Each of the features within a drop will have its own original artwork. The artwork that displays on the front of an NFT will be based on one of the card’s four features, and is selected from the rarest of the four.

The more rare an NFT, the rarer the artwork that will be selected from its categories. In cases where two or more features are tied for highest rarity, one is selected at random.

For each drop, a featured artist will be selected to work on the collection, each bringing their own unique style. Learn more about the [legendary artwork by Ben Kwok](/nemus-docs/nemus-drops/drop-one-the-genesis-drop/legendary-artwork.md) featured in the Genesis Drop.


---

# 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.nemus.earth/nemus-docs/nemus-litepaper/the-nemus-nft/artwork.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.