> For the complete documentation index, see [llms.txt](https://docs.clyrpool.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clyrpool.com/overview/about-clyr.md). # About Clyr ## Overview of Clyr Our mission is to completely transform the pool industry. We believe that our pools should be optimized for energy efficiency based on pool health, and that pool caretakers should only spend time needed to fix issues that can't be automated. We have developed some of the leading smart pool automation and monitoring devices. Our first product, the smart skimmer, entered the market in 2019. The smart skimmer became the first solar powered direct to WiFi pool chemistry monitor. The automation controller entered the market in 2023. Our goal is simplify pool maintenance and reduce energy costs at the pool pad. We are proudly based in Houston, TX. All our products are designed, engineered and built in the USA. {% embed url="" %} --- # 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://docs.clyrpool.com/overview/about-clyr.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.