> 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/captured-photos.md).
# Captured Photos
Every PAVE capture comes with 11 to 13 photos. At times the user may not capture their VIN or Odometer but opt to manually input. You can tell when this has been done when you see a grey box instead of the photo on your Park Page. We are moving towards capturing 4k images when the User has enough connection bandwidth. These strategically angled photos ensure you receive a complete, unobstructed 360 view of every vehicle.
You can also download these photos to use for other purposes like merchandising incoming trades before they arrive. To do this, click on the PHOTOS button on the vehicle listing within your dashboard. A file will download all the captured initial photos with the VIN as the file name.
---
# 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/captured-photos.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.