> For the complete documentation index, see [llms.txt](https://docs.redx-project.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redx-project.com/introductions.md). # Introductions Introductions for REDX White Paper v2.00 ## Introduction The REDX Project leverages Web3 technology to create innovative entertainment experiences and aims to build a sustainable global entertainment economy. With Tokyo Tower as the ground zero, REDX establishes a Web3 hub centered around RED° TOKYO TOWER, where fans, creators, content (IP), investors, and partners come together. Using REDX tokens as the core, we are expanding next-generation entertainment experiences to the world by integrating online and offline interactions. By maximizing the potential of Web3, REDX creates an environment where fans worldwide can easily access entertainment content. Through participatory content creation and consumption, we introduce new value to the entertainment industry. Through these efforts, REDX will realize a new form of entertainment where creators and fans can grow together and support each other. {% embed url="" %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.redx-project.com/introductions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.