> 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/x-twitter.md).

# X (Twitter)

Check X profile activity and attributes to verify social engagement, account authenticity, or specific profile requirements.

#### Setting up X requirements

**Follow or be followed by:**

* In the role editor, click **"Add requirements"** and select **X (Twitter)**
* Choose **Follow or be followed by**
* Enter the username of the account 

**Have something in your profile:**

* Choose **Have something in your profile**
* Select which profile attribute to check:
  * **Name** - Display name (not @username)
  * **Username** - The @handle of the account
  * **Description** - Bio/profile description text
  * **Verified** - Whether account has verification checkmark
  * **Protected** - Whether account is private
  * **Created at** - Account creation date
  * **Followers count** - Number of followers
  * **Following count** - Number of accounts they follow
  * **Tweet count** - Total tweets (including retweets)
  * **Like count** - Total tweets they've liked
  * **Listed count** - Number of public lists they're in
  * **Media count** - Number of media posts shared

For all requirements, customize the requirement name and image if you want, then click **"Add requirement"**.

Members connect their X account and Guild automatically verifies their profile data and social activity.


---

# 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/x-twitter.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.