> 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/scout/scout-dashboard/rekor-carcheck-r.md).

# Rekor CarCheck®

Rekor CarCheck® is a cloud-hosted ALPR web service for application integration. Using this product, you can send images to the Rekor cloud servers for analysis and the returning response will be a JSON document describing the license plates, and vehicle characteristics such as color, make, and body type.

CarCheck can be purchased separately or added in parallel to your Rekor Scout® account. To learn more about CarCheck, please visit our [Rekor CarCheck® product page](https://www.rekor.ai/developers/carcheck) or view the [Rekor CarCheck® documentation](/developers/carcheck/rekor-carcheck-r-overview.md) to learn how to integrate the API into your existing applications.

The image below provides a sample view of the data the [Rekor Scout® Dashboard](/scout/scout-dashboard/overview.md) shows concerning Rekor CarCheck. It also contains a demo for simple image testing and example output.

<figure><img src="https://app.snazzydocs.com/storage/users/LyXaxVR6U0o9QI5U/docs/HCFTSZwZ5EATAFU6/images/blue_camaro_blur.jpg" alt=""><figcaption></figcaption></figure>


---

# 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/scout/scout-dashboard/rekor-carcheck-r.md?ask=<question>&goal=<user_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.