> For the complete documentation index, see [llms.txt](https://nearfox-project.gitbook.io/nearfox-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nearfox-project.gitbook.io/nearfox-whitepaper/introduction-nearfox.md). # Introduction NearFox ### The NearFox platform is not just a website, is not just a website, it is a whole ecosystem that will be filled with different features both for ordinary holders, NFT creators, those who are interested in passive income, and mainly for young artists who want to enter the NFT sphere, create own project, understand how the NFT system works on Aurora, as well as help at every stage of our artist’s promotion. > Collection “NearFox” (\*collection of 444 hand-drawn NFTs on Paras) — Art and culture are part of our life and characterize the society in which we live, it is important to support them and those who work and are interested in this area. Today in fact many people are still facing the challenge of living with the incomes of artistic works. Digitization, artificial intelligence, big data analytics, internet of things, augmented reality, blockchain, and other big developments — these all represent the fourth **industrial revolution 4.0**. --- # 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://nearfox-project.gitbook.io/nearfox-whitepaper/introduction-nearfox.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.