> For the complete documentation index, see [llms.txt](https://docs.guild.xyz/guild/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guild.xyz/guild/how-to-setup-requirements/token-balance.md).

# Token balance

Check whether members hold a certain amount of tokens on a selected blockchain. Perfect for creating token-gating access and tiered memberships.

**Setting up token balance requirements:**

* In the role editor, click **"Add requirements"** and select **Token Balance**
* Fill out the parameters:
  * **Chain** - Select the blockchain where the token is deployed
  * **Token address** - The contract address of the token you want to check
  * **Balance** - Specify how many tokens members must hold using these conditions:
    * **Equal** - Must hold exactly the specified amount
    * **Doesn't equal** - Must hold any amount except the one specified
    * **Greater than** - Must hold more than the specified amount
    * **Greater than or equal to** - Must hold at least the specified amount
    * **Less than** - Must hold fewer than the specified amount
    * **Less than or equal to** - Must hold at most the specified amount
    * **Range** - Must hold an amount within the specified range
* Customize the requirement name and image if you want
* Click **"Add requirement"**

Members connect their wallet and Guild automatically checks their token holdings. If someone sells their tokens and no longer meets the requirement, they automatically lose access to the role.


---

# 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://docs.guild.xyz/guild/how-to-setup-requirements/token-balance.md?ask=<question>&goal=<user_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.