> For the complete documentation index, see [llms.txt](https://docs.lilypad.tech/lilypad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lilypad.tech/lilypad/tooling-plugins-and-integrations/ai-tooling.md). # AI Tooling AI tooling using Lilypad AI tooling provides the essential infrastructure and frameworks that support the development, deployment and monitoring of AI-powered applications. This section highlights tools that help streamline workflows, enhance visibility and enable customization when building with AI on Lilypad, with examples and guides for integrating them into your projects.
Anything LLMGPT Desktop Client for LilypadAnything LLManythingllm.png
RivetAgentic WorkflowsRivetrivet.png
Lilypad Llama3 ChatbotAI-powered chatbot running on the Lilypad Network using Llama3 for intelligent responses.Lilypad Llama3 Chatbotchatbot.png
Lilypad ML WorkbenchA platform for running, fine-tuning and deploying AI models on the Lilypad Network, with support for Jupyter notebooks and multi-module workflowLilypad ML Workbenchml.png
--- # 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.lilypad.tech/lilypad/tooling-plugins-and-integrations/ai-tooling.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.