> For the complete documentation index, see [llms.txt](https://docs.blaze.ong/blaze/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blaze.ong/blaze/creating-your-collection/whitelist.md).

# Whitelist

Add up to two whitelist phases before public mint. Each phase can have a different mint price, start, and end time.

To add a whitelist to your collection's mint, navigate to the `Optional Details` section of the `Mint Details` form.

Click on the `Add Whitelist` button.

Edit the following settings according to your preference:

* **MINTS PER ADDRESS:** number of mints permitted per address (e.g. 3 mints per address means the address is eligible to mint 3 NFTs in total)
* **MINT PRICE:** mint price for the Whitelist phase. This can be the same or different from the Public phase.
* **MINT START:** start time for the mint phase.
* **MINT END:** end time for the mint phase.
* **CSV / TXT OF ADDRESSES:** a .csv or .txt file of the addresses included on the Whitelist. These will be the addresses eligible to mint during the Whitelist phase.

<figure><img src="/files/w0uwW6R4VFBArNKbskq0" alt="" width="563"><figcaption></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://docs.blaze.ong/blaze/creating-your-collection/whitelist.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.