> For the complete documentation index, see [llms.txt](https://docs.eyepop.ai/developer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eyepop.ai/developer-documentation/self-service-training/how-to-train-a-model/previewing-results.md). # Previewing Results The preview experience allows you to test your model in real-world scenarios. Select or drag an image into your preview experience. The image output with bounding boxes will display on the left side of the screen, with JSON outputs on the right. This is another opportunity for you to adjust the confidence threshold, fine-tuning to optimize predictions. At this stage, you have an output and can begin thinking about how you might integrate these results in your product. You can find more information about the types of data that EyePop.ai can return and how they can be integrated in **Developer Documentation**. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eyepop.ai/developer-documentation/self-service-training/how-to-train-a-model/previewing-results.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.