> For the complete documentation index, see [llms.txt](https://p00ls.gitbook.io/token-integrations-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://p00ls.gitbook.io/token-integrations-guide/introduction/token-gating-vs-token-spending.md). # Token Gating vs Token Spending There are 2 ways to create token usage: through token gating and token spending. ### Token Gating Token gating, also known as token-based access control, is a mechanism used to control access to resources, services, or content by requiring individuals to possess a specific token. It is recommended for these use cases: * Exclusive content only for top members * Membership to communities * Exclusive merchandise for your community * Voting * Private text and video chats ### Token Spending Token spending is the use or transfer of digital tokens or coins for various purposes that can range from transactions and payments to accessing specific features or services within an ecosystem. Recommended use cases: * Token Collectibles * Merchandise (physical and digital) * Discounts * NFTs --- # 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://p00ls.gitbook.io/token-integrations-guide/introduction/token-gating-vs-token-spending.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.