> For the complete documentation index, see [llms.txt](https://nfts-101.kyzzen.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/artwork.md).

# Artwork

The first aspect of an NFT project that we generally look at is usually the artwork, as this is the first thing that is usually in front of us or readily available. As we all know, art is extremely subjective, but some questions that you can ask yourself are: 

* Does the art look like it was created by a professional artist? 
* Does it look low-effort or low quality? 
* Does it resonate with you? 

The importance of these questions can differ from person to person, not just whether the person has a strong opinion about art but also if they care much about artwork in an NFT project.

Another factor to consider regarding artwork is whether it looks like a derivative of another project or art collection, or potentially even a copy mint (a direct copy of another artist’s artwork, minted into a new NFT). To help determine this, you can run a simple image search with a few of the NFTs in the collection on [Google](https://www.google.com/imghp?hl=en) and/or other free tools online. One thing we have noted is that these searches may not include results from OpenSea and other NFT marketplaces, hence this risk will always be prevalent but can at least it can be reduced.  An additional step you may take is to check out the project’s Twitter and Discord to see if there have been any claims of copying or similar projects.

<figure><img src="/files/ey8D8QvjbMhJ4Iwl1y2Z" alt=""><figcaption><p>Google Image Search</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 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://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/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.