THE LENS · CONNECTED VEHICLE DATA LAB
Find the documented data route for an insurance decision.
Explore manufacturer-level coverage, public product evidence and insurance use cases—without presenting a model, VIN or signal as verified when it has not been tested.
START HERE
What are you trying to find out?
Returns only routes whose public source names this manufacturer. No model, model-year or VIN compatibility is inferred.
PUBLICLY DOCUMENTED ROUTES6Mercedes-Benz
Manufacturer-level evidence only. This confirms that a public source names the manufacturer or first-party product. It does not confirm any model, model year, VIN, signal, UK contract or live delivery.
View documented routes01 · PROVIDER EXPLORER
Compare documented routes.
Results reflect the public evidence attached to the selected journey. They are not compatibility or procurement confirmations.Aggregator
High Mobility
Connected Car API · Insurance and multi-brand fleets
Source-confirmedUK eligible; contract checkSource conflictChecked 22 Sep 2026
OdometerTrip distanceTrip timestampsLocation / route+5 more documented
Aggregator
Smartcar
Connected Car API · Retail consent and rapid integration
Source-confirmedUK confirmedChecked 22 Sep 2026
OdometerTrip distanceTrip timestampsLocation / route+4 more documented
Aggregator + hardware
Targa Telematics
OEM data platform · Commercial fleet and insurance
Publicly claimedUK eligible; contract checkChecked 22 Sep 2026
OdometerTrip distanceTrip timestampsLocation / route+6 more documented
Data marketplace
CARUSO Dataplace
Data marketplace · European fleet, aftermarket and insurance
Publicly claimedUK eligible; contract checkChecked 22 Sep 2026
OdometerTrip distanceTrip timestampsLocation / route+3 more documented
Aggregator
Motorq
Connected Vehicle Platform · Commercial fleets, rental and leasing
Publicly claimedUK not verifiedChecked 22 Sep 2026
OdometerTrip distanceLocation / routeIgnition and vehicle state+2 more documented
Direct OEM
Mercedes-Benz
Fleet API + Smart Vehicle Data · PAYD, fleet, EV and vehicle status
Source-confirmedUK confirmedChecked 22 Sep 2026
OdometerTrip distanceTrip timestampsLocation / route+7 more documented
DIRECT OEM REGISTER
First-party products, with evidence boundaries explicit.
This register confirms that the public first-party product exists. It does not claim model, VIN, signal or commercial eligibility unless the cited source says so.| Manufacturer | Product | Purpose | UK availability | Primary source |
|---|---|---|---|---|
| Mercedes-Benz | Fleet API | Fleet data packages | UK confirmed | Fleet API |
| Mercedes-Benz | Pay As You Drive | Insurance mileage | UK eligible; contract check | Pay As You Drive |
| Mercedes-Benz | Electric Vehicle Status / Vehicle Status | Smart Vehicle Data | UK eligible; contract check | Fleet API |
| BMW Group | CarData API | Vehicle data | UK confirmed | BMW CarData |
| BMW Group | CarData Streaming | Event stream | UK confirmed | BMW CarData |
| Ford | Ford Pro Data Services | Commercial fleet | UK confirmed | Ford Pro Data Services |
| Stellantis | Mobilisights Vehicle Data Platform | Multi-brand embedded data | UK eligible; contract check | Vehicle Data Platform |
| Tesla | Fleet API | Developer API | UK not verified | Fleet API |
| Volvo Cars | Connected Vehicle API | Developer API | UK not verified | Connected Vehicle API |
“UK not verified” is deliberately different from “unavailable”. Only first-party public documentation is used for direct-OEM product claims.
02 · SIGNAL LAB
Understand the signal—or compare who evidences it.
Absence from public documentation is shown as “not evidenced”, never assumed to be unavailable.SignalPublic evidenceActuarial utilityWhat it enables
Verified cumulative mileage without relying on customer declaration.
Reading cadence and ignition dependency vary by vehicle.Distance at trip or reporting-period level for pay-per-mile and utilisation.
Some feeds derive trips from start/end readings.When exposure occurs: commuting, social hours, overnight and seasonal use.
Timezone and trip-boundary rules must be normalised.Road class, urban density, territory and route-level exposure.
High privacy impact; some feeds expose only endpoints.Speed distribution, road-context matching and driving-style features.
Sampling may be too sparse for event scoring.Traditional telematics behaviour features and event detection.
Embedded feeds are less consistent than calibrated hardware.Separates parked, active and unavailable periods.
Definitions differ for EV-ready and charging states.Fuel use, state of charge, range and charging behaviour.
Battery health is not equally available across brands.DTCs, service warnings, tyre pressure and maintenance indicators.
Diagnostic depth and permissions differ.Potential automated FNOL and incident triage.
Never infer crash access from generic brand coverage.Separates fitted capability from enabled or intervening systems.
Operational intervention data is rarely consistent.Lock, unlock, charge and precondition actions.
Normally unnecessary for pricing.These categories describe the current public evidence base, not measured UK vehicle-parc penetration.
Back to starting question ↑03 · SOURCE ROUTE DECISION
Choose breadth, depth—or continuity.
The right architecture can combine all three rather than force one universal feed.Fastest route to breadth
- One contract and data model
- Reusable consent and activation flow
- Lower integration burden
Trade-off: provider margin, normalisation loss and a lowest-common-denominator signal set.
Best route to depth
- Richest OEM-specific packages
- Clear signal provenance
- Potential volume economics
Trade-off: separate procurement, schema, consent and support for every OEM.
Best route to continuity
- Consistent sampling and behaviour logic
- Older and unsupported vehicles
- Independent data specification
Trade-off: device, installation, logistics, tamper and customer-friction costs.
RECOMMENDED ARCHITECTURE
Aggregate first. Prove the gaps. Integrate selectively.
Multi-OEM APIlaunch coverageCoverage telemetryeligibility · quality · consentDirect OEMvolume + unique signalsHardware fallbackunsupported parc
04 · ACTUARIAL USE-CASE LAB
Turn a product question into a data specification.
The recommendation identifies a starting architecture, candidate providers and the test most likely to expose false confidence.Pay per mile
How much was the vehicle used?
MINIMUM VIABLEOdometerTrip distanceTimestamp
ADDITIONAL VALUELocation / road classPurpose proxy
- Likely route
- Start multi-OEM; consider direct OEM at scale
- Required cadence
- Daily odometer or complete trip ledger
- Candidate providers from the canonical register
- SmartcarUK confirmedHigh MobilityUK eligible; contract checkMercedes-BenzUK confirmedBMW GroupUK confirmed
- Validation test
- Reconcile odometer movement to billed miles.
- Failure mode
- Missing trips, delayed readings and consent lapse create billing risk.
05 · UK COVERAGE METHOD
See how technical reach becomes usable coverage.
Adjust illustrative assumptions to understand why brand counts systematically overstate the addressable insurance book.ILLUSTRATIVE USABLE COVERAGE40.7%
Replace with audited cohort inputsProduct of the five assumptions—not a published UK market estimate.
Publication rule. A defensible result requires a VIN or connected-vehicle cohort joined to the UK parc, with the denominator, observation period and failure reasons reported.
06 · EVIDENCE & GOVERNANCE
Read confidence before coverage.
The same four-level evidence language now appears throughout the Lab, beside the claims it qualifies.The provider describes the product or coverage, but the public detail is insufficient to verify it.
A primary public source names the product, manufacturer, market or data category being shown.
The provider confirms the individual vehicle and required data package as eligible.
The required signal has been received and tested for quality, completeness and latency.
Smartcar · Provider operational evidenceCompatible Vehicles API v3Daily observed make/model/year/powertrain dataset; absence means not yet observed or insufficient dataCompatibility · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentSmartcar · Provider deprecation noticeDeprecated VIN compatibility endpointRetired on 15 September 2026; retained only as a migration warningDeprecated source · checked 2026-09-22 · next automated not scheduled · human review 2026-10-20retiredHigh Mobility · Provider documentationOEM guides and brand pagesNamed OEM guides, markets, models and data points; some availability statements conflictCompatibility · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20Dated Nissan and Hyundai availability announcements conflict with 'yet to be available' banners on some brand pages. Ford shows a similar contradiction. Manual review is required; no availability conclusion is inferred.warningHigh Mobility · Provider announcementNissan vehicle data announcementProvider announcement that Nissan vehicle data is availableManufacturer coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentHigh Mobility · Provider announcementHyundai availability announcementProvider announcement that Hyundai is availableManufacturer coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentTarga Telematics · Provider disclosureOEM data and connectivityNamed OEM relationships and hardware fallbackManufacturer coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentTarga Telematics · Provider announcementHyundai Connected Mobility partnershipEuropean Hyundai data integration with business-user consent; UK package not expressly confirmedManufacturer and signal coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentCARUSO Dataplace · Provider disclosureVehicle manufacturersNamed marketplace manufacturersManufacturer coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentCARUSO Dataplace · Provider announcementHyundai platform integrationHyundai B2B fleet and B2C private-vehicle channels in supported European markets; UK not namedManufacturer and signal coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentMotorq · Provider disclosureConnected Vehicle Platform25+ automotive brands claimed; public examples named, but no complete model or UK registerProduct and manufacturer coverage · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentMercedes-Benz · Direct OEMFleet APICars and vans; trip, EV, behaviour, health and remote packagesDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentMercedes-Benz · Direct OEMPay As You DriveInsurance-oriented distance and trip endpoint productDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentBMW Group · Direct OEMBMW CarDataBMW and MINI API/streaming; UK supportedDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentFord · Direct OEMFord Pro Data ServicesConnected commercial-vehicle data servicesDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentMobilisights / Stellantis · OEM data unitVehicle Data PlatformEmbedded data from Stellantis brandsDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentTesla · Direct OEMFleet APIOfficial developer API; UK insurance suitability not verifiedDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentVolvo Cars · Direct OEMConnected Vehicle APIOfficial developer API; UK commercial suitability not verifiedDirect OEM product · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20currentDfT / DVLA · Official statisticsVehicle licensing statisticsUK vehicle-parc denominator, including make/model filesParc · checked 2026-09-22 · next automated 2026-09-29 · human review 2026-10-20current
Data hygiene and publication gates
Canonical provider and manufacturer IDs drive the public UI, recommendations and export. Every published coverage claim needs a primary source, checked date, next review and UK-status label. Model, model-year, VIN and live-signal claims are prohibited unless the evidence reaches that exact level. Missing citations, duplicate brands, stale UK evidence and orphan recommendations block publication; absence is recorded as “not evidenced”, never “unavailable”.