> For the complete documentation index, see [llms.txt](https://hello.kodadot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello.kodadot.xyz/generative/generative-drops/drop-party.md).
# Drop Party
To make things a bit more exciting, we recently added a Party Kit to our Drop page. We don't want you to feel alone; it's droptime, so join us at this party! 🚀
## What is this Drop party?
When a new drop is launched, after you open it, you may see more cursors moving around the page. Those are fellow collectors who are exploring the page with you! Once you meet them, you know that you are not alone. We are having a party with collectors! 🥳
## What can you see?
* **Fellow collectors and their activity 😎**
* **Status:** whether they are generating, minting, or just moving around
* **Their art**: An NFT they are generating/minting,
* **Amounts in DOT**: how big a spender are they, and how much they spend on the NFTs
Here, you can see all the components:
## Not a party person?
Don't worry; you can turn off our Drop Party feature if you prefer to buy your art alone. Open the sidebar, head to settings - interface, and turn off the party mode.
---
# 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://hello.kodadot.xyz/generative/generative-drops/drop-party.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.
