> For the complete documentation index, see [llms.txt](https://castleoverlord.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://castleoverlord.gitbook.io/whitepaper/dev-team-and-partner/paras.md). # Paras Paras is an NFT marketplace that focuses on digital collectibles. Paras thrives upon bringing conventional collectibles to crypto space. Paras started with digital art cards that were inspired by real-world trading cards that have been bulletproof and forever lasting since they were introduced back in the 80s. Paras believes that every single physical art form needs to be stored and digitized to keep it future-proof. Paras, an all-in-one digital collectible marketplace, is eager to diversify the assets to digital collectibles. By building the platform under NEAR and IPFS/Filecoin, Paras wants to track the ownership of every single collectible in their platform. Through these solutions, Paras validates ownership and gives access to every purchase and mint to the public. Running on top of NEAR, a scalable blockchain, Paras offers very cheap and fast transactions for users. Unlike other marketplaces, Paras are putting collections forward instead of a single art release. Paras believes that collecting collectibles like digital art cards do not only attract crypto collectors but also conventional trading card collectors. With the current artists they have, Paras is confident in their ability to capture the essence and excitement of collecting a set of cards. Paras also aims to increase the NFT's value by including background stories or lore as they think that visuals can be enhanced through this approach. --- # 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://castleoverlord.gitbook.io/whitepaper/dev-team-and-partner/paras.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.