> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/general.md). # General - [Velogic's Support Policy](https://docs.velogicfit.com/general/support-policy.md): Velogic's email-first support policy and how to get help - [Using Bar XY Cartesian Coordinates](https://docs.velogicfit.com/general/bar-xy-coordinates.md): Complete guide to using Bar XY Cartesian coordinates for bike fitting and frame comparison. Learn about Reach and Stack metrics and why Bar XY provides more accurate frame sizing. - [Downloading statements](https://docs.velogicfit.com/general/downloading-statements.md): If you need detailed statements for your accounting record, you can download these through our website. - [Changing your credit card](https://docs.velogicfit.com/general/changing-credit-card.md): If your credit card expires, or you need to change the credit card used for your Velogic subscriptions, you can do that yourself easily via our web application. --- # 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.velogicfit.com/general.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.