> ## Documentation Index
> Fetch the complete documentation index at: https://docs.korint.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Telematics : Drivequant

> Driving-behaviour scoring for usage-based motor insurance

Telematics measures how a policyholder actually drives and turns it into a score. The Korint platform uses this scoring for usage-based motor insurance, where the premium reflects real driving behaviour rather than only static risk factors. The current telematics provider is **DriveQuant**, and the integration is used on the VTC products (Yeet and Axece).

***

## What It Does

The platform connects to the telematics provider to:

* **Register drivers**: enrol a policyholder's driver with the provider so their trips can be tracked
* **Retrieve driving scores**: collect the driving-behaviour scores produced from those trips
* **Average scores over a period**: combine individual scores into an average for a given period, which is the figure used for pricing

The resulting average score feeds mid-term **repricing**: the premium for a usage-based product is adjusted during the policy's life to reflect how safely the driver has been driving.

***

## Vendor-Agnostic by Design

The telematics provider is integrated through a vendor-agnostic adapter. The platform speaks to a single, provider-neutral interface (register a driver, get scores, average them), and DriveQuant sits behind it as one interchangeable implementation.

<Note>
  Because the product depends only on the neutral interface, the telematics provider can be swapped for another without changing how the product prices or reprices.
</Note>

***

## Related Documentation

* **[Repricing](/concepts/core-lifecycle/repricing)**: How premiums are adjusted mid-term for usage-based products
* **[Third-Party Integrations Overview](/concepts/integrations/overview)**: Overview of all external system integrations
