> For the complete documentation index, see [llms.txt](https://premint.gitbook.io/vulcan/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://premint.gitbook.io/vulcan/products/bots/premint-bot/interacting-with-the-bot.md).

# Interacting with the bot

Admins can always type `/` to see a list of commands available:

## /vulcan\_post\_raffle \[any premint link]

Admins can use this command to embed a PREMINT raffle directly in Discord.

## /premint

Users can type `/premint` in any channel to see if they are registered in the PREMINT list for your project.

Since we're not passing in an address, we're relying on whether the user linked their Discord in PREMINT.

## /premint \[wallet]

If a user did not link their Discord, we recommend they pass their ETH wallet address or ENS name to the bot.

For example:

> `/premint 0x064DcA21b1377D1655AC3CA3e95282D9494E5611`

Or:

> `/premint rhynotic.eth`

This command will add the role you setup earlier to the user.


---

# 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://premint.gitbook.io/vulcan/products/bots/premint-bot/interacting-with-the-bot.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.