> For the complete documentation index, see [llms.txt](https://docs.hiwaifu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiwaifu.com/product-guides/creating-chatbots/chatbot-attributes/chatbot-visibility.md). # Chatbot Visibility The ***Visibility*** setting controls who can interact with your AI chatbot. Here are the visibility options available: ### Public Choosing this option means your chatbot can be interacted with by anyone, and it will appear in public listings and search results. This is the choice to make when you want to share your creativity and imagination with the world and want the community to interact with your chatbot. ### Private If you want your chatbot to be your little secret, this is the option for you. A private chatbot is visible only to you. Even if you share a link to it, nobody else will be able to access or chat with your chatbot. {% hint style="danger" %} **Note:** Even though hidden chatbots may not be visible to the general public, they are still visible to our moderators. If a chatbot violates our community guidelines, it will be removed, irrespective of its visibility status. We encourage you to familiarize yourself with our \[[community guidelines](/community-guidelines.md)] to ensure a safe and positive experience on our platform. {% endhint %} --- # 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.hiwaifu.com/product-guides/creating-chatbots/chatbot-attributes/chatbot-visibility.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.