> For the complete documentation index, see [llms.txt](https://metadoosh.gitbook.io/metadoosh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metadoosh.gitbook.io/metadoosh/doosh-drops.md). # Doosh Drops DoosHDrops is a product in which you will be kept informed of the latest releases in the Nft's markets, in the Ethereum, Polygon, Cardano, and Solana networks, and also its events section keeps you informed of the upcoming events to be held in the world related to cryptos and Nft’s, also creators and developers will be able to publish their new projects at a very low cost and accessible to everyone. If you are a lover of digital art and you are thinking about creating your own NFT's collection and you do not know where to start this space is for you, at DoosHDrops Studio DoosH we put at your disposal our team of designers and developers, to help you from A to Z with your Nft's project, from the initial design to its launch. --- # 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://metadoosh.gitbook.io/metadoosh/doosh-drops.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.