> For the complete documentation index, see [llms.txt](https://docs.childsafetymarket.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.childsafetymarket.org/readme.md). # Overview **Child Safety Supply (CSS)** is the commercial discovery and distribution arm of the broader child safety ecosystem. It exists to help parents, caregivers, and professionals confidently identify tools and resources that reduce risk and improve child safety outcomes. CSS operates as a curated marketplace, not a traditional e-commerce store. Rather than pushing transactions, it prioritizes clarity, trust, and informed decision-making. Products and resources are selected based on their safety purpose, relevance, and alignment with evidence-informed child safety practices. The intent of CSS is to serve as a central place where the public and professionals can discover, evaluate, and access child safety solutions without sales pressure or confusion about intent. --- # 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.childsafetymarket.org/readme.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.