> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/copyright.md). # Copyright ©2026 GXC, LLC. All rights reserved. The documentation on this site is protected by copyright. No part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means — electronic, mechanical, photocopying, recording, or otherwise — without the prior written permission of GXC. **Trademarks** The names of GXC's products are trademarks of GXC. The names of other products mentioned on this site may be trademarks or registered trademarks of their respective companies. **Disclaimer** The documentation on this site is produced by GXC for the use of its customers. The information provided is subject to change without notice and may not cover all details or variations in equipment, or address every possible issue related to the installation, operation, or maintenance of the product. While every effort has been made to ensure accuracy, GXC disclaims liability for any difficulties arising from the interpretation of the information contained herein. --- # 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.gxc.io/copyright.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.