> 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/tutorial-summary.md). # Tutorial Summary **Congratulations!** All of the Vehicle Spy tutorials have been completed! A solid foundation for working with Vehicle Spy has been built. Feel free to keep browsing through the rest of the Vehicle Spy documentation to learn more about the additional features the software has to offer. Intrepid Control Systems, Inc. will be adding to these tutorial files regularly. If there are any suggestions for additional topics or modifications to existing topics, please reach out let us know. Interested in more training? Intrepid offers a complete schedule of training courses for Vehicle Spy as well as other topics such as CAN, LIN, automotive ethernet, gateway builder, and many more. For more information about training, please visit the learning center on our website. [Back to Tutorial Introduction](/vspy-3-documentation/vehicle-spy-tutorials.md)![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/next.gif) [Back to Documentation Introduction](/vspy-3-documentation/readme.md)![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/next.gif) --- # 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/tutorial-summary.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.