> For the complete documentation index, see [llms.txt](https://devhub.autograb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devhub.autograb.com/uk-autograb-api-doc/vehicle-data/vehicle-data-basics.md). # Vehicle Data Basics Get the level of detail you need on the vehicle you want. The Vehicle Data API set allows you to find descriptive information on a vehicle at the level of granularity you require. This API requires [authentication](/uk-autograb-api-doc/authentication/api-key.md) and an appropriate license attached to it.

Recall Search

Perform a recall check on a vehicle's registration

Recall Search

MOT & Tax Search

Get a vehicle's registration MOT and tax status

MOT & Tax Search

Vehicle History

Use this if you require a history-style description of the vehicle's pricing and listing history.

Vehicle History

Factory Build Data

Get the vehicles build sheet to inform your user interface.

Factory Build Data

Factory Fitted Options

Get the options fitted to a given vehicle by VIN.

Factory Fitted Options
--- # 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://devhub.autograb.com/uk-autograb-api-doc/vehicle-data/vehicle-data-basics.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.