> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/8.-use-cases-and-deployment-scenarios/8.2-development-of-use-cases-by-entertainment-genre.md).
# 8.2 Development of use cases by entertainment genre
Music and Live Events
* NFT-based ticketing for resale control and authentication
* Fan Club DAOs enabling setlist voting and project co-creation
* GET Pay cashless purchases at venues
* NFT sales of concert footage with embedded proof of participation
Film and Visual Content
* DAO-based community production support (scripts, cast voting)
* NFT-based screening rights for premium experiences
* Exclusive "behind-the-scenes" content sales as NFTs
* Stage greeting participation rights tokenization
Idol/promotion activities
* NFT voting systems for fan-driven idol promotion
* Contribution-based rankings via GET Miles accumulated from tracked SNS activities
* On-site staking check-ins for fan rewards
* Special edition tipping and lotteries during virtual lives
Game/e-sports
* In-game NFT item sales and holder-only events
* Spectator voting influencing tournament rules
* Score/contribution-based GET rewards
* Team support through token contribution and return design (Predictive Vote)
RWA (real estate and real assets)
* Tokenization of real estate and art through NFTs
* Sales of experiential rights (e.g. hotel stays, exclusive venue access)
* Tokenized traditional crafts and fine art NFTs with real-world pairing
* Royalty distribution for artists upon secondary sales
---
# 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.global-entertainment-token.org/8.-use-cases-and-deployment-scenarios/8.2-development-of-use-cases-by-entertainment-genre.md?ask=&goal=
```
`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.