> For the complete documentation index, see [llms.txt](https://docs.rekor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rekor.ai/rekor-discover-r/vehicle-insite/reports.md).
# Reports
Rekor Discover's reports analyze the collected data using A.I. and machine learning to provide powerful roadway intelligence and insights utilizing easy-to-read graphics and information.
To create a report, click Create New Report.
Select the source of the data. Then click Next Step.
Select the locations for the report from either all the devices int he area, or select devices.
If only some devices will be used, select the sites from the map. Click Next Step.
Then select the specific sites from the list. Click Next Step.
Select the edge devices. Click Next Step.
Select the date range. The choices are yesterday, the last 7 days, the last 30 days, or a custom date range.
Then select the days of the week that will be applicable for the report. The choices are all days, weekdays only, weekends only, or custom days.
Finally provide a name for the report. Then click Finish.
---
# 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.rekor.ai/rekor-discover-r/vehicle-insite/reports.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.
