Full transparency

Which signals, which makes, which market.

CarConnective reads vehicles directly through owner-consented OEM APIs — no dongles, no OBD hardware. The matrix below shows exactly which signals are available for which makes in the US and UK, so you know precisely what you're buying. We expand it every time an OEM opens a new endpoint.

The eight signals

What each column means.

Signal availability is determined by what each OEM exposes via their API — not by what is technically possible on the vehicle. Where a signal is partial, it varies by model generation or trim within that make.

Odometer

Verified, software-read mileage — available across nearly every connected make on both US and UK markets.

Oil Life %

Remaining oil-life percentage — the primary service trigger for ICE vehicles. Broadly available on US market; not widely exposed by European OEM APIs.

Tire Pressure

Per-tire TPMS readings. Available on most connected makes; a subset of OEMs do not expose individual tire pressure via their API.

Fuel Level

Tank percentage. Available on ICE and hybrid vehicles across the majority of supported makes in both markets.

Battery & Charge

State of charge, estimated range, charge status, and — for select OEMs — charging session details (voltage, amperage, wattage). Available on every connected EV and phev.

Diagnostics (DTC)

Live fault codes read the moment they trip. Available in the US on GM brands (Chevrolet, Buick, Cadillac, GMC), Stellantis/FCA, and Nissan. In the UK: Jaguar, Land Rover, Polestar, and a limited subset of Hyundai, Alfa Romeo, and Fiat.

Location

Last-known vehicle coordinates, owner-consented. Available broadly across connected makes in both markets.

Service History

OEM service records via API. Currently available in the US market on Ford, Lincoln, Toyota, Lexus, Mazda, and Volkswagen. Not available in the UK.

OEM compatibility matrix

Every make. Every signal. No surprises.

Select your market below. Where a make has a footnote number, additional context appears beneath the table.

Confirmed broad supportVaries by model / yearEVElectric vehicles onlyNot available
MakeOdometerOdometerOil Life %Oil LifeTire PressureTire PSIFuel LevelFuelBattery & ChargeBatteryDiagnostics (DTC)DTCsLocationLocationService HistoryHistory
TeslaEV1
ChevroletGMEV
BuickGM
CadillacGMEV
GMCGM
FordFord2EV
LincolnFordEV
JeepStellantis
RAMStellantis
ChryslerStellantis
DodgeStellantis
Alfa RomeoStellantis
FiatStellantisEV
ToyotaToyotaEV
LexusToyotaEV
MazdaToyota3
NissanNissan4EV
VolkswagenVW GroupEV
AudiVW GroupEV
BMWBMW GroupEV
MINIBMW GroupEV
Mercedes-BenzMercedesEV
HondaHondaEV
HyundaiHyundaiEV
KiaHyundaiEV
SubaruSubaru
VolvoVolvoEV
RivianEV5
  1. Requires Virtual Key setup for commands. Most comprehensive EV signal set available.
  2. Service history available via OEM API. DTCs not available; oil-life threshold is primary service trigger.
  3. Mazda service history available via OEM API.
  4. LEAF EV signals are among the most complete in the platform.
  5. Bluetooth pairing required for commands.
A note on diagnostics

DTCs are targeted, not universal.

Diagnostic trouble codes require the OEM to expose fault data via their API — something only a minority currently do. In practice, oil-life thresholds and mileage velocity cover the bulk of service-drive intelligence for the makes that don't expose DTCs directly.

US market · DTC support

GM, Stellantis & Nissan

Live fault codes confirmed on Chevrolet, Buick, Cadillac, GMC, Jeep, RAM, Chrysler, Dodge, Alfa Romeo, and Fiat (Stellantis/FCA group), and Nissan — the three OEM groups that currently expose DTC data via their consumer APIs.

UK market · DTC support

JLR, Polestar & selected Stellantis

Confirmed on Jaguar, Land Rover, and Polestar. Limited diagnostic data on select Hyundai, Alfa Romeo, and Fiat models. UK OEM API coverage for fault codes is narrower than the US — we flag this clearly and expand it as APIs open.

Consent-first architecture

The customer connects their car.

Every reading in the matrix above is accessed through an explicit owner-consent flow — the same pattern used to link a bank account. The customer sees every permission, per vehicle, and can disconnect in one tap. No OEM credentials are stored. Nothing is installed in the vehicle. If the owner revokes consent, reads stop immediately.

What we read
  • Telemetry signals explicitly authorized by the owner
  • Only the signals listed in the matrix above
  • Nothing from the cabin, contacts, or communications
What we never read
  • Owner PII beyond what the relationship already holds
  • Anything after the owner disconnects
  • Signals the owner has not explicitly authorized
See a real connection

Watch signals stream in from a live vehicle.

We'll connect a real car in your demo — you see the signals land on the customer record and watch the actions fire. Then we map coverage across your actual parc.