> For the complete documentation index, see [llms.txt](https://docs.dacity.store/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dacity.store/crew-card-and-avatar-studio.md).

# Crew Card and avatar studio

Optional ways to represent the community.

<figure><img src="https://3451933-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fee8m3C1HCRumYG94B8mY%2Fuploads%2FErSe54cZ6leNjOLViVdQ%2FDacity-Motion-Crew.gif?alt=media&amp;token=e8de40a5-32da-4052-ae96-78363e87996b" alt=""><figcaption></figcaption></figure>

**Optional ways to represent the community.**

## Your Crew Card

Approved eligible wallets can use the available Crew Card flow in their wallet-linked profile. The card uses the current Dacity Store basket design and a share preview prepared for X. Use the website’s Share control to open the normal X compose flow with your prepared link and message.

Generating or sharing a card does not issue another $10 grant. A public card and its share link can be viewed by anyone you share them with. If an old preview is cached by a social app, check the current prepared link rather than repeatedly creating new claims.

## The optional avatar studio

The [avatar studio](https://dacity.store/avatar-studio) lets you create a GTA VI avatar using the project’s available character artwork and controls. Choose a character and look, adjust the available style and crop options, then download the result.

The studio is a creative extra. You do **not** need a custom avatar, pump.fun profile or Crew Card to apply for whitelist benefits. Official GTA VI artwork remains the property of Rockstar Games and Take-Two.

[Open the studio](https://dacity.store/avatar-studio) · [My Crew](https://dacity.store/marketplace#my-crew)


---

# 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.dacity.store/crew-card-and-avatar-studio.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.
