Insurance is priced on the vehicle, but too often it's priced on what the customer says about the vehicle. Free-text make and model, a guessed value, an undisclosed write-off — each is a mis-rating or a fraud opportunity. Validating the vehicle from its registration at quote time closes that gap. This guide explains how insurers and brokers use vehicle data to price accurately and spot risk before binding.
The problem with customer-declared data
When a quote form asks the customer to type in their vehicle details, you inherit their errors and their incentives. Common failure modes:
- Mis-keyed make/model/trim that changes the risk band.
- Undisclosed modifications or spec that materially affect value and risk.
- Undisclosed write-off history that surfaces only at claim time — after you've been on cover.
- Deliberate misrepresentation to lower the premium.
Every one of these is preventable at quote time with a registration lookup.
Validate the vehicle from the number plate
Instead of trusting free text, resolve the vehicle from its registration and pre-fill the quote:
- Vehicle Details confirms make, colour, fuel, engine size, year, CO₂ and current tax/MOT status — the factual basis for rating.
- Spec & Options returns the factory equipment actually fitted, so you rate on verified spec rather than a customer's description.
Pre-filling from the plate also reduces quote abandonment — the customer types a registration instead of a dozen fields — while improving data quality. It's a rare win-win: a smoother journey and a more accurate risk picture.
Check provenance before you bind
The higher-value control is provenance. A Provenance Check surfaces the markers that change whether — and at what price — you should offer cover:
- Insurance write-off category (A/B/S/N) — a previously written-off vehicle is a different risk.
- Stolen marker on the Police National Computer.
- Outstanding finance and mileage anomalies.
Running provenance as part of the quote flow means write-off and theft history is discovered before binding, not at first notification of loss. That's fewer disputed claims, less fraud leakage and cleaner underwriting.
A quote-time validation flow
A typical integration:
- Customer enters a registration.
- Call Vehicle Details → pre-fill and confirm the vehicle; fast first response for a smooth UX.
- Call Spec & Options where trim materially affects rating.
- Call Provenance Check as a risk gate before a firm quote or at bind.
Because every product returns the same normalized JSON envelope and runs off one API key, this is a single integration. See how it maps to the insurance solution, and try the response shapes in the sandbox.
Pay-per-lookup fits variable quote volume
Quote volume is spiky. VehicleMatic is pay-per-lookup on credits with no contract, and you're only charged on a successful lookup — so validation cost tracks quote volume rather than a fixed licence. Model it on the pricing page.
Frequently asked questions
Can I pre-fill a quote form from a number plate? Yes — a Vehicle Details lookup returns the core attributes to pre-populate and confirm the vehicle.
When should I run the provenance check — quote or bind? Either. Many insurers do a light validation at quote and a full provenance gate at bind; the API supports both.
Does this reduce fraud? It removes the easiest misrepresentations (wrong vehicle, hidden write-off) by validating against official data instead of customer input.
Explore the insurance solution or start with Provenance Check.