> For the complete documentation index, see [llms.txt](https://docs.tempbot.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tempbot.xyz/tempbot-v4.md). # TempBot v4 Looking for a powerful and versatile Discord bot to manage your community's memberships? Look no further than TempBot! With easy-to-use integrations, license keys, and button & reaction roles, TempBot allows you to manage your memberships quickly and intelligently, making it the perfect choice for business services on Discord. Plus, with TempBot's customizable notification messages, detailed logging, and extensive knowledge base, you'll never be left in the dark when it comes to managing your community. And with more features in the works, TempBot is constantly evolving to meet the needs of its users. So why wait? Start using TempBot today and streamline your Discord server management in no time! --- # 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.tempbot.xyz/tempbot-v4.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.