> 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/overspeed.md).
# Overspeed
The Overspeed report displays data from speed segments. In order to view the Overspeed data, you must first set up the segments in the Speed module.
Click the Speed module in the left frame then click Create Speed Segment.
Select the cameras for the speed segment. Click Next Step.
Set the segment details. This will auto-populate from any previous lane calibrations. You may also change the parameters, if desired.
Then enter the name of the segment and click Finish.
Go to Reports>Create New Report then select Overspeed.
Select the segment that was just created.
Select the date range.
Select the days of the week.
Enter the report name, then click Finish.
The Overspeed Report displays a map of the speed segment, the amount of vehicles traveling over the speed limit, and a visual of the speed limit and average speed.
---
# 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/overspeed.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.
