Transparency

Methodology

Every number VINLytix shows you, and exactly how it was produced. If a calculation cannot survive being published, it should not be on the report.

Four measures, four questions

A VINLytix report carries four separate readings, and keeping them apart is the single most important decision in how it works:

Vehicle Assessment — is there anything concerning about this vehicle, in the data we could actually check?
Deal Score — is the seller’s asking price attractive against the market for comparable vehicles?
Data Coverage — how much of the relevant record we were able to verify.
Valuation Confidence — how solid the market price estimate is.

These are never averaged, never combined into a single label, and never allowed to move one another. An earlier version of this report fused the first two into phrases like “High Risk / Poor Value”, which asserts two unrelated claims in one breath. A sound car at a silly price is not dangerous, and a cheap car with a salvage title is not low risk. Only the final verdict combines them, and it does so explicitly.

Vehicle Assessment

Categorical, never a number. A 0–100 risk score would imply a precision that public vehicle data cannot support, and would invite averaging against the Deal Score — exactly the fusion this separation exists to prevent. There are four states:

Insufficient Data — no check produced a usable result.
No Major Concern Found In Checked Data — the checks that ran found nothing concerning.
Review Recommended — something is worth looking into.
Significant Concern Found — a verified record that should change your approach.

The second state is scoped deliberately. “No major concern found in checked data” does not mean the vehicle is clean, accident-free, mechanically sound, safe, or in good condition. It means the specific checks listed on the report found nothing — and the report always lists what was not checked alongside what was.

Unknown is never negative

This is the rule that governs the whole assessment. Mileage not entered, history not checked, a recall lookup that failed, no mechanical inspection — all of these are unknown, and none of them is evidence against the vehicle. They appear in a visually distinct “still to verify” section, never in a list of findings.

Only a verified result may move the assessment toward concern. This matters because the alternative quietly punishes sellers who supply less information, and punishes us for the limits of our own data sources.

Why vehicle age is not scored

It used to be, and that was wrong. A 23-year-old vehicle is not automatically a bad vehicle or a bad deal — its age is already reflected in the expected-mileage calculation, in which comparable vehicles get selected, and in what those comparables actually sell for. Scoring age again on top of all three charged the vehicle a second and third time for the same fact.

It also produced a concrete failure. A 2003 sedan submitted as a bare VIN, with nothing else known, once scored 25/100 — because vehicle age was the only component that could be computed, and a weighted mean of one component is that component. Model year is still shown as context. It is no longer scored.

The Deal Score

A single figure from 0 to 100, where higher is a better price. It answers exactly one question: how attractive is the seller’s asking price against the current market for comparable vehicles? It says nothing about the vehicle.

It requires both halves

A number is shown only when there is an asking price and a market estimate with enough confidence behind it. Missing either, the report says Deal Score unavailable and names what is missing. There is no fallback that scores a price against a value we could not establish.

How the number is calculated

Purely from the asking price’s position against the market estimate, on a piecewise-linear curve:

25% or more below the estimate → 100
At the estimate → 65
25% above → 20
50% or more above → 0

The curve is deliberately gentler below the estimate than above it: paying 10% over market costs you money, while paying 10% under merely saves some, and a seller’s price is a ceiling you negotiate down from. Because the function is strictly decreasing in price, a lower asking price can never score worse than a higher one against identical market evidence — a property the tests assert across the full range rather than assume.

Why mileage, trim and location are not scored again

Because they are already inside the market estimate. The VINLytix Market Intelligence Engine selects and weights comparable vehicles by mileage, trim, model year and distance before it computes anything. Scoring those factors a second time inside the Deal Score would double-count the same facts — a high-mileage car would be marked down once by the comparables it gets matched against, and again by a separate mileage penalty.

Score bands

90–100 — Excellent Deal
80–89 — Good Deal
65–79 — Fair Deal
50–64 — Above Market
0–49 — Poor Deal / Overpriced

65 is exactly the market estimate, so “Fair Deal” begins at the market price and everything above it is a genuine discount. The word risk never appears in a Deal Score band — risk is a property of the vehicle, and an expensive car is not a dangerous one.

The confidence gate

Even with an asking price in hand, a score is not shown from weak market evidence. Where Valuation Confidence is Insufficient Data, the Deal Score is suppressed entirely. Where it is Low, the score is shown with an explicit low-confidence warning — suppressing it as well would discard a usable signal built on thin but real evidence, while hiding the thinness would overstate it. Medium and High support normal scoring.

Vehicles that cannot be compared normally

If a verified record shows a salvage, junk, flood or similar branded title, the Deal Score is suppressed and the report says standard market comparison may not apply to this vehicle. Branded-title cars trade in a different market from the clean-title listings an estimate is built from, and without this gate a salvage vehicle would score as an excellent deal purely because it is cheap. That is the most dangerous false positive this product could produce.

What the Deal Score is not

It is a presentation heuristic for comparing listings against one another. It has not been validated against transaction outcomes, and VINLytix makes no claim that it is statistically predictive. The bands are user-experience thresholds chosen for legibility, not empirically derived cut-offs. It is also not a statement about the car: a low price on a badly maintained vehicle still scores well.

Data Coverage

A separate figure from 0 to 100, answering a different question: how much of the relevant vehicle record VINLytix was able to verify. The domain list and its weights are fixed, so coverage cannot be inflated by shortening the checklist.

Domain	Weight	Requires
VIN identity	10	Year, make and model resolved from the VIN.
Vehicle specifications	15	Body style, engine, fuel, drive type, transmission.
Manufacturer and assembly plant	5	Building manufacturer and plant location.
Safety recall campaigns	15	Published campaigns for the vehicle line.
Recall repair completion	10	Whether recall work was done on this specific car. Not available through the public NHTSA API.
Mileage analysis	10	Requires the user to supply an odometer reading.
Market valuation	20	Requires a licensed pricing provider.
Accident, title and ownership history	15	Requires a licensed history provider.

Two domains — recall repair completion and full history — are currently unreachable for every report, which places a hard ceiling of 75% on Data Coverage. That ceiling is deliberate and is not hidden. Without a valuation provider connected, the practical ceiling is 55%.

Deal Score and Data Coverage are independent. A vehicle can score 88 on 45% coverage. That combination is not a contradiction, it is the honest answer: what we could see looks good, and we could not see much.

Mileage analysis

Expected mileage accumulates on a tapered schedule, because annual mileage genuinely falls as a vehicle ages:

Years 1–5 — 13,500 miles per year, close to the average annual mileage per US light-duty vehicle reported by the Federal Highway Administration
Years 6–10 — 11,000 miles per year
Years 11 and beyond — 8,000 miles per year

A flat rate would compound its error until it became absurd: 13,500 a year across 23 years predicts over 310,000 miles, so a 168,000-mile 2003 sedan would be scored “below average” against a figure almost no car of that age reaches. The taper keeps the comparison meaningful across the whole age range.

Age is the current calendar year minus the model year, with a floor of half a year so a current-model-year vehicle does not produce a division by zero.

Verdicts are set on the ratio of actual to expected:

Below Average — under 0.75x
Average — 0.75x to 1.15x
Above Average — 1.15x to 1.5x
Very High — over 1.5x

This compares one odometer reading against a population average. It is not odometer fraud detection, which requires a history of recorded readings from a licensed provider. VINLytix will never suggest a rollback on the basis of this calculation.

Valuation Confidence

A third measure, separate from both of the above, and the three answer different questions:

Deal Score — how attractive the deal looks
Data Coverage — how much of the vehicle record was verifiable
Valuation Confidence — how solid the price estimate is

A car can score 85, on 70% coverage, from a valuation we have Low confidence in. Those are three separate facts and the report shows all three.

Confidence is an additive score over five signals:

Comparable listings (30) — 200+ scores full; 50–199 scores 22; 10–49 scores 12; fewer scores 4. Zero if the provider does not report a count.
Trim match (20) — full when the provider matched the exact trim, 6 when it explicitly could not, 10 when it does not say.
Mileage input (20) — full when an odometer reading was supplied, zero otherwise. Mileage is one of the largest price factors.
Local market (15) — full when the value is anchored to a local market, 8 when a ZIP was given but the figure is national, zero when no ZIP was supplied.
Data recency (15) — full at 7 days or fresher, 10 up to 30 days, 3 beyond that, 5 when the provider does not publish a dataset date.

Bands: High 75+, Medium 50–74, Low 25–49, Insufficient Data below 25. A provider that reports its own low confidence overrides an otherwise optimistic total — it knows things about its model that we cannot see.

When confidence is Insufficient Data, the report still classifies the asking price but withholds the negotiation range. A dollar figure presented as advice implies a valuation solid enough to negotiate against, and lending that precision to a number we have already said we do not trust would be the wrong kind of confident.

The VINLytix AI Market Estimate

VINLytix does not have a secret dealer price book, and it does not ask a language model what a car is worth. It estimates market pricing the way a careful buyer would if they had all afternoon: by finding vehicles like yours that are actually for sale right now, discarding the ones that are not really comparable, and taking the middle of what is left.

The difference between that and a guess is evidence. Every estimate on a report is accompanied by the listings it was computed from, with links. If the number looks wrong to you, you can go and check.

How comparable vehicles are found

The search starts as narrow as your VIN allows and widens only when the narrow search did not find enough:

Level 1 — exact year, make, model and trim, within a local radius.
Level 2 — exact year, make and model. Trim relaxed.
Level 3 — within one model year, wider area.

Make and model are never relaxed at any level. A thin search for an Accord does not quietly start pricing Camrys. The radius expands through 25, 50, 100 and 250 miles before falling back to a national search, and the report always states which level and which radius produced the figure — twelve listings at Level 1 supports a very different claim from twelve at Level 3.

If no ZIP code was supplied there is no local market to search, so the result is labelled a National market estimate and carries lower confidence.

What gets excluded

Most listings a search returns are not usable comparables. These are removed before any arithmetic, and the report says how many went and why:

Monthly payments and lease rates advertised where a sale price should be
Placeholder prices — a published figure of a dollar or two meaning “call for price”
Salvage, flood, rebuilt and otherwise branded vehicles
Parts-only and non-running cars
Auction bids, which are not asking prices
New vehicles
A different make, model, or materially different trim
Model years outside the range the search level permits

The lease filter matters more than it sounds. A monthly payment accepted as a car price does not look like an error in the output — it looks like a bargain.

Duplicates

The same physical car is routinely advertised on the dealer’s own site and on two marketplaces. Counting it three times would both inflate the comparable count that drives confidence and let one unrepresentative vehicle move the estimate three times as far as it should. Duplicates are detected by published VIN, by canonical URL, by shared photograph, and finally by matching vehicle, mileage and price at the same seller.

How the price is calculated

The headline figure is a weighted median of the accepted asking prices, after removing statistical outliers.

Median, not average. Three optimistic dealership listings can drag an average anywhere. They can only move a median to the next car along.
Weighted. A near-identical car three miles away is better evidence than a different trim two states over, and the arithmetic should say so. Weights come from a similarity score over model year, mileage, trim, distance, listing recency and how complete the listing data was.
Outliers removed. Prices beyond 1.5 times the interquartile range are excluded — the extra digit a dealer typed by mistake. Below six listings this is skipped, because with four prices one genuinely expensive car looks like an outlier and removing it is just discarding evidence.
Typical asking range is the interquartile band: the middle half of what these cars are advertised at.

All of that arithmetic is ordinary deterministic code. No language model computes any figure on a VINLytix report. An AI may help read a messy listing title or normalise a creatively-written trim; it never produces, adjusts or checks a price.

Mileage and location

There is no universal cents-per-mile constant here, because there is no universal cents-per-mile constant in the world — it differs by segment, age and model. If the retrieved listings contain enough of a mileage spread to measure a price-per-mile relationship, that measured rate is used and the report says so. If they do not, no mileage adjustment is applied and confidence drops instead.

The same principle governs geography. Rather than applying invented regional multipliers, the engine prefers local listings and lets the data show what the local market actually is.

When there is no estimate

Three comparable listings is the floor. Below that, the report says “Not enough current market data to produce a reliable estimate” and shows no figure at all. Two listings can be thousands of dollars apart with no way to tell which is typical, and publishing their midpoint would be a fabrication dressed as an analysis.

Confidence above that floor considers the number of comparables, how similar they are, whether trims were stated, whether the search stayed local, how far the search had to widen, how tightly the listings agree on price, whether more than one source corroborates them, and how old they are. Roughly: 11 or more close local listings can reach High; 6 to 10 sits around Medium; 3 to 5 is Low.

The result is an estimate derived from current asking prices. It is not an official valuation, not a certified value, and not a guaranteed sale or purchase price. Asking prices are what sellers want, which is not always what cars sell for.

Where each money figure comes from

Every valuation figure on a report is tagged with its provenance, and the two tags mean genuinely different things:

Provider data — the pricing provider supplied this number.
VINLytix estimate — the provider did not supply it, so VINLytix derived it. The calculation is printed underneath the figure, every time.

Where a provider returns only a retail estimate, the derived figures use these conventional rules of thumb for the US used-car market. They are published here precisely so a reader can discount them appropriately — they are not measurements:

Personal Buyer Target — the retail estimate. A private buyer keeping the car pays about market value.
Dealer Buy Target — retail less 15%, a conventional allowance for reconditioning, overheads, risk and resale margin. This is not a wholesale quotation. A real trade offer depends on the car’s condition and the buyer’s stock needs.
Quick Sale Estimate — retail less 8%, the discount typically needed to sell privately in days rather than weeks.
Suggested Listing Range — retail plus 4–9%, leaving room to negotiate without being filtered out of buyers’ price searches.

A figure VINLytix cannot derive defensibly is shown as unavailable rather than guessed, and a modelled figure is never rendered without its basis.

Why this value?

Where a provider breaks its estimate into factors — mileage, trim, local demand — the report shows them. Where it does not, the section says so. VINLytix does not generate statements like “trim adds $900”: that claim needs data behind it, and inventing a plausible attribution is exactly the kind of confident-sounding fiction this product exists to avoid.

Data freshness

Two dates, kept deliberately apart on every source label:

Checked — when VINLytix queried the source. Always known.
Data updated — when the source’s own dataset was last computed. Shown only where the provider publishes it, and omitted rather than guessed otherwise.

Querying a source today does not mean its data was updated today, and the report never implies that it does.

Price classification

Where both an asking price and a market valuation exist, the signed percentage difference against the estimate is classified as:

Great Deal — 10% or more below the estimate
Good Deal — 3% to 10% below
Fair Price — within 3% either way
Above Market — 3% to 10% above
Overpriced — more than 10% above

The recommended negotiation range is anchored just below the point estimate, and is never allowed to fall below the pricing provider’s own lower bound — suggesting an offer outside the provider’s stated range would be advice we cannot support.

VIN validation

Every VIN is checked for length, for the letters I, O and Q which never appear in a VIN, and against the ISO 3779 position-9 check digit. The checksum transliterates each character, applies positional weights, and takes the sum modulo 11.

A failed check digit is reported as a warning, not a rejection. The check digit is mandatory for vehicles built to North American specification and optional elsewhere, so legitimately imported vehicles routinely fail it.

Recall campaigns are never a “major” red flag

Campaigns are matched by year, make and model, so the count reflects the vehicle line’s history rather than the condition of the car in front of you. A 2003 sedan can legitimately return two dozen campaigns, nearly all of them repaired years ago under the free-repair obligation.

Treating a high count as a major issue would contradict the caveat printed beside it and would condemn essentially every older vehicle on the strength of data we have already said cannot support that conclusion. Recall findings are therefore capped at needs attention, with the report directing you to the only source that can actually answer the question — a franchised dealer checking the individual VIN.

The final verdict

A synthesis layer, and only that. It combines the Vehicle Assessment, the Deal Score where one exists, Data Coverage and Valuation Confidence — without altering any of them. All four stay visible separately on the report, and the verdict never feeds back into them: a serious vehicle concern does not reduce the Deal Score, and an attractive price does not soften the Vehicle Assessment.

That separation is what makes the awkward combinations expressible:

Vehicle fine, price good → Worth Considering
Vehicle fine, price high → Vehicle Appears Worth Considering, But Price Is Too High
Vehicle needs review, price good → Attractive Price, But Review Vehicle Concerns
Verified serious concern, any price → Major Vehicle Concern — Low Price Does Not Remove the Risk
Nothing verified yet → Not Enough Information Yet

A verified significant concern outranks everything, including an excellent price. The Deal Score is left exactly as it is — the price genuinely is attractive — and the verdict declines to recommend anyway. A cheap salvage car is cheap for a reason, and that reason is recorded against the vehicle.

Evidence is presented in three visually distinct groups: what we found, what needs attention, and what is still to verify. The third group is never styled as a warning, and it is never empty — an independent mechanical inspection always appears there, because VINLytix has not driven this car, put it on a lift or heard it start.

Changes to this methodology

These calculations will change as providers are connected and as the scoring is refined. Material changes will be reflected on this page. See which sources are currently active.