> For the complete documentation index, see [llms.txt](https://docs.bitbond.com/asset-tokenization-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitbond.com/asset-tokenization-suite/token-tool/intro-token-tool/paying-fees-on-token-tool.md). # Paying Fees on Token Tool Token Tool is a Web3 app where payment upon check out takes place in the native cryptocurrency of the network being used. When users decide to use Token Tool to configure and deploy smart contracts, they need to connect their wallet and complete payments in crypto by confirming the transaction in their wallet. Our [pricing page](https://tokentool.bitbond.com/pricing) contains a detailed breakdown of the costs for all Token Tool functions and features. Purchasing cryptocurrency can prove to be a challenging to users who are not familiar with the space. It can also be difficult to investors looking to invest in token sales that were created with Token Tool. Many wallet providers like MetaMask, offer a user-friendly interface to easily buy crypto directly from their apps. We put together a guide to walk you through the process of [how to buy crypto on MetaMask](https://www.bitbond.com/resources/buy-crypto-on-metamask/). You can use the guide for your own reference, or refer your investors to that guide if you're [conducting a token sale](https://docs.bitbond.com/asset-tokenization-suite/token-tool/create-token-sale) with Token Tool. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bitbond.com/asset-tokenization-suite/token-tool/intro-token-tool/paying-fees-on-token-tool.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.