> For the complete documentation index, see [llms.txt](https://devhub.autograb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devhub.autograb.com/nz-autograb-api-doc/other-products-and-resources/brand-guidelines.md). # Brand Guidelines How to use AutoGrabs brand correctly The following guidelines help developers to use AutoGrabs’s brand and assets correctly and consistently where approved to do so. ### Naming Apps and Integrations When naming apps and integrations that use AutoGrab data, please follow these guidelines: * Use a unique name for your application or integration * Do not use “AutoGrab” in the name of your application or integration * Clearly state that the integration is built by you — and not AutoGrab * Do not use a name that is confusingly similar to AutoGrab or infringes on any other trademarks ### Logo & Brand Usage The logo and wordmark are the most prominent elements of the AutoGrabs brand and it’s important to use them correctly. Detailed instructions for the usage of our brand assets are provided via our dedicated brand usage guide. {% file src="/files/1NIgog31IXcPPjaxSExx" %} --- # 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://devhub.autograb.com/nz-autograb-api-doc/other-products-and-resources/brand-guidelines.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.