> For the complete documentation index, see [llms.txt](https://support.highlight.xyz/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.highlight.xyz/knowledge-base/for-developers/nft-contracts/erc721generativeonchain.md).

# ERC721GenerativeOnchain

The ERC721GenerativeOnchain is very similar to the ERC721GeneralSequenceImplementation. The main difference is that we store the generative code URI on the contract. Additionally, this contract allows you to invoke a \`setCustomRenderer\` method which allows you to point your contract to a custom metadata renderer. This enables things like complex onchain rendering use cases. This contract allows you to invoke \`setTokenURI\` to override the metadata for specific tokens. 

Finally, this contract also implements an on-chain file storage system, which can point to files stored on-chain through our file deployer. You can add files, remove files, get files, get addresses of where file contents are stored, and get a string of the file. These files can then be pulled into your custom renderers and used to create on-chain works involving formats like HTML or SVG.

### Contract link

{% embed url="<https://github.com/highlightxyz/hl-evm-contracts/blob/main/contracts/erc721/ERC721Generative.sol>" %}


---

# 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://support.highlight.xyz/knowledge-base/for-developers/nft-contracts/erc721generativeonchain.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.