> 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/class-count-and-speed/editor.md). # CCS Overview Rekor Discover's Class, Count, and Speed application, along with Rekor Edge Series systems, utilize state of the art AI and edge processing to automate the safe and efficient capture of FHWA 13-bin vehicle classifications, vehicle counts, and vehicle speeds. By analyzing live, high-resolution video of active traffic, Rekor Discovers Class, Count, and Speed application delivers per vehicle records (PVR) in both real-time and historic reports. This enables cities, states, and municipalities to better plan and engineer safe and reliable roadways for the future. Leveraging proprietary Rekor Edge devices, systems are deployed quickly and easily on the side of the road, keeping workers out of unsafe conditions. AI edge data processing is then utilized to capture comprehensive and accurate per vehicle records including full FHWA 13-bin classification, vehicle count, and speed. Download the Rekor Discover CCS User Guide here: {% file src="/files/Z3PX7sjrNdqp65EgLYUO" %} {% embed url="" %} --- # 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/class-count-and-speed/editor.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.