> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/agency-white-label/getting-started.md). # Getting started The Agency Solution empowers you to host AppMySite on your domain maintain a full white-label identity, and serve an unlimited number of customers. The is your launchpad to building and managing apps for your clients through the AppMySite Agency solution. Whether you’re setting up your first client project or looking to streamline your workflow, this category provides essential guidance on creating, configuring, and organizing apps under your agency account. You’ll find step-by-step articles covering: * How to create new apps for your clients * Setting up app details and branding * Navigating the agency dashboard * Understanding user roles and client-specific permissions This section is designed to help agency partners establish a smooth foundation before diving into more advanced features like app customization, publishing, and team collaboration. Start here to ensure every app you create is structured, consistent, and ready to scale. --- # 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.appmysite.com/agency-white-label/getting-started.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.