> For the complete documentation index, see [llms.txt](https://docs.nftdelegation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nftdelegation.com/overview/use-cases.md).

# Use Cases

## Active (canonical) use cases

| #N        | Use Case                                                              |
| --------- | --------------------------------------------------------------------- |
| 1         | All                                                                   |
| 2         | Minting / Allowlist                                                   |
| 3         | Airdrops                                                              |
| 4         | Voting / Governance                                                   |
| 5         | Avatar Display                                                        |
| 6         | Social Media                                                          |
| 7         | Physical Events Access                                                |
| 8         | Virtual Events Access                                                 |
| 9         | Club Access                                                           |
| 10        | Metaverse Access                                                      |
| 11        | Metaverse Land                                                        |
| 12        | Gameplay                                                              |
| 13        | IP Licensing                                                          |
| 14        | NFT rentals                                                           |
| 15        | View Access                                                           |
| 16        | Manage Access                                                         |
| 17        | Mint To Address                                                       |
| 18        | Team                                                                  |
| 19        | Artists                                                               |
| 20 to 949 | Reserved by NFTDelegation.com for future Active (Canonical) Use Cases |

* Use cases #1 to #19 are active canonical (official) use cases.
* \#20 to #949 are reserved for additional Active (Canonical) use cases, to be added from time to time by NFTDelegation.com.

## Special use cases

| #N         | Use Case                               |
| ---------- | -------------------------------------- |
| 950 to 997 | Reserved for Future Special Use Cases  |
| 998        | Delegation Management (Sub-delegation) |
| 999        | Consolidation                          |

* Special Use Cases are not captured by Use Case #1 ("All").
* \#950 to #997 are reserved for future Special use cases.
* \#998 is for Delegation Management (Sub-delegation) (giving the right to another address to add or remove delegations on the initial address's behalf).
* \#999 is for Consolidation (linking addresses together).

## Application specific use cases

| #N    | Use Case                       |
| ----- | ------------------------------ |
| 1000+ | Application-specific use cases |

* \#1,000+ are available to any team who wants to create an application-specific use case.
* Any team can call the updateUseCaseCounter() function to increment/create another use case for their own use.


---

# 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.nftdelegation.com/overview/use-cases.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.