> For the complete documentation index, see [llms.txt](https://wp.jannavi.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.jannavi.net/jn-token/jn-token-event-features.md). # JN Token Event Features Discover how JN Tokens enable diverse event-related activities, reinforcing the JAN-Navi brand's presence in the eSports and Mahjong communities. * **eSports Tournaments Hosting:** Utilize JN Tokens to organize eSports tournaments, allocating tokens for player rewards and covering operational expenses, thus fostering competitive play within the community. * **Offline Event Organization:** Deploy JN Tokens to facilitate and sponsor offline events, such as meetups and community gatherings, enhancing real-world interaction among users. * **Brand Enhancement:** The multifaceted utility of JN Tokens enhances brand awareness and loyalty, solidifying JAN-Navi's reputation in the digital and physical gaming spheres. --- # 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://wp.jannavi.net/jn-token/jn-token-event-features.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.