> For the complete documentation index, see [llms.txt](https://docs.paveapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paveapi.com/how-pave-works/detected-damages.md).
# Detected Damages
{% file src="/files/War5G7NzAmxTt8rUO3qM" %}
### Detected Damages by PAVE
PAVE's inspection engine analyzes images to detect 350 specific damages of different degrees of severity that cover most cosmetic damages on 249 components that make up the anatomy of over 23,000 light commercial and passenger vehicle models sold over the past 15 years in North America that PAVE’s models were developed from.
These damages are mainly concentrated on the exterior and wheels and tires.
NUMBER OF DAMAGES PER COMPONENT TYPE
PAVE REPAIR TYPES
PAVE has no known limitations on its ability for detecting damages from 2D images on any vehicle type, body style or color. However, other environmental factors that can impact PAVE's results are:
Captures of vehicles in the dark or at night. \
Captures of cars or trucks during significant rain or snowfall. \
Captures of images when standing in direct sunlight.
---
# 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.paveapi.com/how-pave-works/detected-damages.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.