> For the complete documentation index, see [llms.txt](https://phemex.gitbook.io/phemex-web3-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phemex.gitbook.io/phemex-web3-whitepaper/features/phemex-soul-pass.md). # Phemex Soul Pass The Phemex Soul Pass (PSP) is a Soulbound Token (SBT) that can be minted on the Ethereum network. It is the first-ever soulbound token to be used by a major cryptocurrency exchange for the purpose of decentralizing ownership and assembling a grassroots community of collaborators. Phemex Soul Passes can be held on any ETH-compatible wallet such as Metamask, Portis, or a new wallet created on Phemex. As a SBT, the Phemex Soul Pass is non-transferable and does not have tradeable value. However, it grants access to pre-mining Phemex Tokens and contains important credentials related to your Phemex account including your [xPT](/phemex-web3-whitepaper/features/phemex-token/xpt.md) balance. Qualified Phemex accounts can mint one Phemex Soul Pass each. --- # 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://phemex.gitbook.io/phemex-web3-whitepaper/features/phemex-soul-pass.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.