> For the complete documentation index, see [llms.txt](https://docs.xhashtag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xhashtag.io/the-basics/introducing-.soul-domains/utilities-of-.soul-domains.md). # Utilities of .Soul Domains On the Web3 space, Soul Names have a number of utilities, which are constantly evolving as the ecosystem grows. **Here are some of the key utilities of your lifetime free, transferable .Soul domain name:** * An easy reference to your complex wallet address * Compatible with all kinds of SBTs, they allow a single point of access to a user’s Web3 reputation * Unlock special access to smart contracts based on the user’s aggregated reputation * An identification mechanism on the xHashtag dApp * Compatible with a number of wallets and addresses * As they are Ethereum-based, they can be traded on NFT exchanges such as OpenSea * They can be used in conjunction with xHashtag’s Soul Page --- # 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://docs.xhashtag.io/the-basics/introducing-.soul-domains/utilities-of-.soul-domains.md?ask=&goal= ``` `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.