# Checking for tokens

In the first step, I suggest you set @HuilityBot as an admin in your chat room. Give permissions to delete users and request +chat\_id. This will come in handy later

<figure><img src="https://content.gitbook.com/content/J2V0omksi0wZNflNYZOe/blobs/vBppruACSp8DBpQDjI7c/image.png" alt="" width="464"><figcaption></figcaption></figure>

Huility bot is able to check for tokens in both private and public chats. To do this, you need to go to the "Add Chat" section

<figure><img src="https://3950932126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ2V0omksi0wZNflNYZOe%2Fuploads%2FgDjdGKXH77kABw1iGHf8%2Fimage.png?alt=media&#x26;token=6aa980f3-2177-410e-8ebb-e05af940ac2c" alt="" width="308"><figcaption></figcaption></figure>

Next, you must select the token to be checked.

The next step is to choose a chat room, **private** or **public**.

*What is the difference between Private and Public? Public chat is open and can be accessed via an accessible link. Private chat can be accessed only by a special invitation link.*

<figure><img src="https://3950932126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ2V0omksi0wZNflNYZOe%2Fuploads%2FgRwT9PQgpABueHSALo0B%2Fimage.png?alt=media&#x26;token=8c14acbf-dcb7-4e6d-be9f-7305cbda962a" alt=""><figcaption></figcaption></figure>

In the next field you can insert +chat\_id that we got earlier

<figure><img src="https://3950932126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ2V0omksi0wZNflNYZOe%2Fuploads%2FN7IqtYj1BCpqvsIc5iaN%2Fimage.png?alt=media&#x26;token=1f9d6234-a31b-4ba3-b96d-e4615752d1e6" alt=""><figcaption></figcaption></figure>

Then you need to specify the number of tokens to be set as a pass. If it is a private chat, the link to the invitation will be available in the button "List of available privates" -> "selected token to check"

<figure><img src="https://3950932126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ2V0omksi0wZNflNYZOe%2Fuploads%2FRrNZATODZHkovvZiieGP%2Fimage.png?alt=media&#x26;token=4b1fdec7-2da9-482e-aba0-2e6e0e5d1d37" alt=""><figcaption></figcaption></figure>

In public chat the mechanics work differently. All messages will be deleted until the user connects his/her wallet to the bot and acquires the necessary number of tokens.

<figure><img src="https://content.gitbook.com/content/J2V0omksi0wZNflNYZOe/blobs/AGwVHafSHNvdxP0wDSrw/image.png" alt="" width="458"><figcaption></figcaption></figure>

In one of the updates, we started supporting the ability to support simultaneous token and NFT validation. You can add NFT address verification in bot settings


---

# Agent Instructions: 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:

```
GET https://bolt-foundation.gitbook.io/bolt-ecosystem-eng/boltfather-docs/another-functions/checking-for-tokens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
