> For the complete documentation index, see [llms.txt](https://artify.gitbook.io/artify-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://artify.gitbook.io/artify-whitepaper/contract-details/contract/tokenomics-and-tax.md). # Tokenomics & Tax Artify $AFY has a total supply of 5 trillion with 0 tokens burned, 0 tokens vested, and 0 tokens set aside for the team. 100% of the tokens were added to initial liquidity at launch. Artify operates on a 5% buy & sell tax, which is broken down into the following: Buy Tax * [x] 4% goes into the marketing wallet, funds will be used for advertising, buybacks, & Extra liquidity as needed * [x] 1% goes into the liquidity pool, strengthening the floor of Artify Sell Tax * [x] 3% goes into the marketing wallet, funds will be used for advertising, buybacks, & Extra liquidity as needed * [x] 2% goes into the liquidity pool, strengthening the floor of Artify --- # 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://artify.gitbook.io/artify-whitepaper/contract-details/contract/tokenomics-and-tax.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.