> For the complete documentation index, see [llms.txt](https://neotechai.gitbook.io/neotechai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neotechai.gitbook.io/neotechai/key-features.md). # Key Features **3D Asset Creation:** * **Technology**: Utilizing Smart City® technology, we create precise 3D models and point-cloud data. * **Exclusive Access**: Asset holders gain access to these models for their projects and benefit from ecosystem-driven data growth. * **Unique Ownership**: Each asset is unique and can only have one owner, who benefits from the asset's integration into our interactive virtual platform, including potential advertisement revenue. * **Custom Creation**: Clients can request our custom scanning service to generate 3D replicas tailored to their preferences. **Marketplace and Trading:** * **Seamless Compatibility**: Our assets are compatible with major marketplaces and can be traded within and outside our ecosystem. * **Secure Data Storage**: Data is securely stored on IPFS and our dedicated servers, accessible only to data owners within our ecosystem. * **Decentralized Transactions**: Users can mint, trade, or rent assets on our marketplace by connecting decentralized wallets, with no personal information stored. **Renting and Subscribing:** * **Rental Income**: NFT holders can rent out their assets to other participants within the ecosystem, generating revenue. * **Subscription Model**: Users can subscribe to use unowned or unminted assets for a limited time. **Data Rarity Levels:** * **Common Data:** Basic assets from NeoTech’s database. * **Rare Assets:** More exclusive assets such as landmarks. * **Legendary Assets:** Iconic landmarks available through auctions. * **Business Assets:** Custom projects for businesses with specific benefits. **$NEOT Token Economy:** * **Primary Currency**: $NEOT tokens facilitate value exchange, serving as the primary currency for purchasing data and services. * **Governance and Voting**: Token holders can vote on future collections and scan locations, shaping the marketplace and the future of the NeoTech project. * **Platform Access**: The token will be the key asset that users must hold in their wallets to access our platform, purchase advertisements, and request scanning services. * **Revenue from Appreciation**: Token holders benefit from the appreciation in value as NeoTech generates revenue. **Interactive Virtual Platform:** * **Immersive Experience**: A WebGL-based game on our platform allows users to explore 3D assets interactively. * **Multi-Mode Exploration**: Features single-player and future multiplayer modes, asset placement, and advertising opportunities. * **Collaborative Decision-Making**: Users and holders of $NEOT will have the chance to access our virtual platform, get transported into any environment available on our marketplace, explore assets together, discuss potential fits for their interests and ventures, and influence asset releases and scanning priorities. --- # 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://neotechai.gitbook.io/neotechai/key-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.