# Introduction

The trip analysis API transforms GPS data collected by a smartphone or any other telematics system into actionable driver and vehicle analytics.

This API is automatically queried by the mobile SDKs as soon as a trip is completed. The results are returned, after a few seconds, to the SDK and can also be transmitted via a [push data service](/push-services/push-data.md) to a third-party server.

The API provides a broad range of indicators that depends on your subscription. DriveKit's trip analysis API provides more than 200 indicators per trip. They are organized by categories so that you can choose the ones that best suit your use case. The categories of driving indicators are listed below. 

Data that represent the driver's behavior:

* Eco-driving score.
* Safety score.
* Distraction score (phone use).
* Speed limits score.

Data that measure the impact of driving behavior on the vehicle:

* Fuel consumption.
* Pollutant emissions.
* Tires and brakes wear.

Additional data describing the context of the trip:

* Departure and arrival adresses and dates.
* Average speed.
* Driving context.
* Weather.

The Trip analysis component also contains an accident detection feature that uses the smartphone's sensors to automatically detect if the vehicle has been involved in a crash. Smartphone-based accident detection allows you to: 

* offer a driver assistance solution integrated into your application; 
* access accurate data to speed up claims management.

{% hint style="info" %}
We recommend you to test this component in the [DriveKit Demo App](/master.md#the-drivekit-demo-app) before you integrate it in your application.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.drivequant.com/trip-analysis/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.