> For the complete documentation index, see [llms.txt](https://goattrading.gitbook.io/dojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://goattrading.gitbook.io/dojo/features/profiles-and-leaderboard.md).

# Profiles and Leaderboard

Profiles allow users to keep track of their holdings and share their holdings with others. Going to the dashboard will show you all tokens you hold, all tokens you’ve created, and all of your open Auto Sells.

If you’d like your profile to be public you can add an avatar, bio, and social media links. Anyone following that link can then also see your tokens owned and created. If you don’t add any information your profile will not be visible on the site. If you’re on the leaderboard, someone clicking on your profile will simply redirect them to a blockchain explorer showing your holdings.

The leaderboard shows top holders based on the USD value of their tokens. It shows account details and allows users to click on the top profiles to learn more. Users who are high up on the leaderboard will be easily visible and highly regarded by every user of the site!


---

# 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://goattrading.gitbook.io/dojo/features/profiles-and-leaderboard.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.