Government-authoritative · No driver PII · DPPA-clear

Where our vehicle data actually comes from.

Every figure traces back to an authoritative public source — EPA fueleconomy.gov and NHTSA (recalls, NCAP, vPIC) — cleaned and cross-referenced by VehDB. No driver, owner or registration PII. No DPPA-regulated data.

Coverage: 1,795 records · 562 cars · 0 with EPA economy.

provenance
# Every field carries its origin
{ "mpg_combined": 28,
  "co2_gpm": 322,
  "source": "EPA fueleconomy.gov" }
{ "open_recalls": 2,
  "source": "NHTSA (live)" }
# What you will NOT find
PII → none · no owner, no VIN history, no DPPA data

Our sources

Authoritative public datasets, plus VehDB's own cleaning and cross-referencing.

Source What we use License & cadence
EPA — fueleconomy.gov Fuel economy (city/highway/combined MPG), annual fuel cost, CO₂ grams/mile, greenhouse-gas score, EV range. U.S. public domain · refreshed on new model-year publication
NHTSA — Recalls Live recall campaigns by vehicle — component, summary, remedy and campaign number. U.S. public domain · read live
NHTSA — NCAP Crash-test ratings — overall, frontal, side and rollover stars. U.S. public domain · read live
NHTSA — vPIC Vehicle product information catalog — make/model/year decoding and attributes. U.S. public domain · refreshed on dataset update
VehDB — Cleaning & cross-referencing Normalization, deduplication, UUID assignment, and tire fitment geometry linking specs to compatible tire sizes. Provided under your VehDB plan · continuous

Base URL: https://api.vehdb.com/v1

From raw government data to one clean catalog

The authoritative source is the floor. The cross-referencing is the value.

Cleaned & normalized

Inconsistent make/model spellings, units and fuel-type labels across federal datasets are reconciled into one consistent schema you can query reliably.

Cross-referenced on one UUID

Specs, EPA economy, live recalls and tire fitment for a vehicle all hang off a single stable UUID — no second lookup, no fuzzy joins on your side.

PII-free by design

We only ingest vehicle and public safety/economy data. No owner, registration or driver information ever enters the system — nothing DPPA-regulated.

For compliance teams

Provenance is a compliance advantage

Insurers, lenders and compliance teams need to prove where data came from. Because VehDB derives from government-authoritative sources and carries no PII and no DPPA-regulated data, you can adopt it without the privacy review that consumer-data vendors trigger. See how it fits compliance and insurance workflows.

Evaluate VehDB for business

Data sources FAQ

Provenance, compliance and update cadence.

VehDB sources data from government-authoritative public datasets: the EPA's fueleconomy.gov for fuel economy, CO₂ and greenhouse-gas figures, and NHTSA for recall campaigns, NCAP crash-test ratings and vPIC vehicle decoding. VehDB then cleans, normalizes and cross-references these into a single UUID-addressed catalog, and adds tire fitment geometry.
No. VehDB contains vehicle specifications and public safety/economy data only. There is no driver, owner or registration PII, and no DPPA-regulated personal data. We do not provide per-VIN history, ownership or title records.
Recalls and NCAP ratings are read live from NHTSA, so they reflect the latest campaigns. Specifications and EPA fuel economy are refreshed as the underlying government datasets publish new model-year data. Each source's cadence is listed in our sources table.
The underlying EPA and NHTSA datasets are U.S. government works in the public domain. VehDB's cleaning, cross-referencing and tire fitment geometry are provided to you under your VehDB plan. For insurers, lenders and compliance teams, government-authoritative provenance with no PII is an advantage, not a liability.

See how we compare to raw NHTSA vPIC, or read the vehicle data for business guide.

Authoritative sources. No PII. 1,795 records.

EPA economy, live NHTSA recalls and NCAP, plus VehDB cleaning and tire fitment — provenance you can put in front of a compliance team. Free tier: 100 calls/mo, no card.

Operated by Savas OÜ (Tallinn, Estonia — EU) · GDPR-compliant · Billing by Stripe · Terms · Privacy