> For the complete documentation index, see [llms.txt](https://wherls.gitbook.io/wherls/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wherls.gitbook.io/wherls/what-is-usdwherls.md). # What is $Wherls $WHERLS is the native utility token of the Wherls ecosystem — a decentralized platform that merges an NFT marketplace, wallet, crypto exchange, staking protocols, and gamified features into a single, cohesive user experience. More than just a token, $WHERLS acts as the fuel of the Wherls ecosystem. It enables users to: * Buy and sell NFTs on the marketplace * Pay transaction and service fees * Stake tokens to earn rewards * Participate in affiliate and referral programs * Access exclusive features such as Super Masternodes * Vote on governance decisions in future DAO implementations Built on the Binance Smart Chain (BEP-20), $WHERLS benefits from fast transaction speeds, low fees, and high compatibility with existing crypto infrastructure. The token is designed to drive value creation within the ecosystem while incentivizing community growth, long-term holding, and decentralized participation. --- # 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://wherls.gitbook.io/wherls/what-is-usdwherls.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.