> For the complete documentation index, see [llms.txt](https://alphabot-docs.gitbook.io/alphabot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alphabot-docs.gitbook.io/alphabot/raffles/entry-requirements.md).

# Entry Requirements

All raffle types can have requirements that the user must complete in order to register for that raffle. Requirements are optional when you create a raffle, but please note that only data from the selected requirements will be collected (e.g. you'll only get entrants' Twitter usernames if you select the `Connect Twitter` requirement). Requirements are set up when creating a raffle and can be changed at any time by the creator of the raffle until it is finalized. These include:

* Verifying NFT holdings, along with multipliers to assign additional entries based on the number of NFTs they hold.
* Minimum ETH balance requirements.
* Validating Discord membership and roles, along with the ability to assign additional entries to specific roles.
* Requiring Twitter engagement, including follows, likes, and retweets.
* Collecting Telegram usernames and verifying channel or group membership.
* Free-form text field inputs.
* Visit a web page.
* Email collection.
* Password protection.
* Additional CAPTCHA for added anti-bot measures.


---

# 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://alphabot-docs.gitbook.io/alphabot/raffles/entry-requirements.md?ask=<question>&goal=<endgoal>
```

`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.