> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/generative-ai/chat-bots.md). # Chat Bots A chatbot is the most common shape a generative model takes in front of a user, and building one draws on agents, GPT models, and intent recognition. This page points to those notes and then to the chatbot survey section. The same notes are in [Agents](/generative-ai/agents.md), [GPT](/generative-ai/large-language-models-llms.md), and [Intent Recognition](/natural-language-processing-nlp/intent-recognition.md). ### CHAT BOTS The notes above cover the models; the missing piece was a survey of chat bots themselves. A list of chat bots, with their pros and cons and example code, used to sit here; that address now points to an unrelated site and is kept at the end of the page. ## Deprecated links {% hint style="warning" %} These links and images no longer work. The original wording is kept here. A same-resource copy, when one was checked, is used above. {% endhint %} * A list of chat bots, pros and cons, example code. This address now points to an unrelated site: --- # 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://www.mlcompendium.com/generative-ai/chat-bots.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.