> For the complete documentation index, see [llms.txt](https://bitgigz.gitbook.io/bitgigz-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bitgigz.gitbook.io/bitgigz-docs/bgz-token/usecase.md). # Usecase One use case of the BGZ token is for payments and transaction fees. Clients and freelancers who use the BGZ token to transact on the platform will receive discounts on transaction fees, which will help incentivize them to use the token. This will also help to drive demand for the token, which could potentially increase its value over time. Another use case for the BGZ token is for advertising on the platform. Clients who want to promote their project or services on BitGigz can do so by purchasing advertising space using BGZ tokens. This will create demand for the token, as clients will need to acquire it in order to advertise on the platform. In addition, the BGZ token can be used to access premium features and services on the platform. For example, freelancers can use BGZ tokens to access tools and resources that will help them to build their brand and market their services more effectively. Clients can use the token to access a pool of high-quality freelancers and to manage their projects more efficiently. As the platform grows and the demand for the BGZ token increases, the value of the token may appreciate, providing potential benefits for investors. This could be further enhanced by the token burning mechanism that was mentioned earlier, where a portion of the tokens used for payments will be permanently removed from circulation, decreasing the overall supply of the token. Overall, the BGZ token has a range of potential use cases and benefits, including access to premium features and services, and the potential for appreciation in value as demand for the token increases. These factors could make the token an attractive investment opportunity for those looking to participate in the growth of the BitGigz platform. --- # 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://bitgigz.gitbook.io/bitgigz-docs/bgz-token/usecase.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.