> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/readme.md). # Welcome to the Vehicle Spy Help Documentation These documents were created to help Vehicle Spy users at every level of experience. ### New or potential users: If you are a new Vehicle Spy user or maybe just gathering information about the tool, check out the [Vehicle Spy Applications Tour](/vspy-3-documentation/vehicle-spy-introduction/vehicle-spy-overview/vehicle-spy-tour/vehicle-spy-tour-1-bus-monitor.md). These pages give a short summary of Vehicle Spy and its many possible applications. Also, these pages provide a way to quickly find information about specifications and hardware requirements. Explore the [Vehicle Spy Tutorials](/vspy-3-documentation/vehicle-spy-tutorials.md) section. These tutorials were put together to help make learning the Vehicle Spy basics a breeze. Complete these exercises and a solid foundation will be built as work with Vehicle Spy begins. ### Everyone: Search through Vehicle Spy's extensive documentation for detailed information about Vehicle Spy's capabilities. Read detailed text and look at informative diagrams and screen shots.\ \ If it has been a while since last using Vehicle Spy, feel free to look over the tutorials again.\ \ If information about other products is needed, visit the [Vehicle Network Interface Hardware](/vspy-3-documentation/vehicle-network-interface-hardware.md) section. --- # 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.intrepidcs.com/vspy-3-documentation/readme.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.