An honest comparison · vPIC is free & authoritative

Vehicle data API vs NHTSA vPIC.

vPIC is the free government authority for VIN decoding — and for plenty of projects it is exactly what you need. VehDB is vPIC cleaned and enriched, for production: a consistent schema with EPA economy, live recalls, NCAP and tire fitment pre-joined on one UUID.

Try VehDB — free Where our data comes from

No card required. We will tell you when vPIC is the better choice.

NHTSA vPIC

Free, authoritative VIN decode, straight from the government source.

  • Free & public
  • Gov-maintained authority
  • Raw, you normalise it
VehDB

vPIC cleaned, enriched and pre-joined on one UUID.

  • Consistent schema
  • EPA + recalls + tire fitment
  • MCP server, SLA & support

First, the honest part

NHTSA vPIC is one of the best free datasets in the industry. It is the authoritative source for VIN decoding, it is government-maintained, and it costs nothing. If your job is "decode this VIN against the official record" and you are happy to normalise the output yourself, use vPIC directly.

VehDB does not try to out-authority vPIC. We build on top of it — cleaning the schema and pre-joining the data you would otherwise stitch together from EPA, NHTSA recalls, NCAP and tire-fitment sources. That is the trade: vPIC wins on free raw authority; VehDB wins on production-readiness.

Side by side

A factual breakdown. Both columns earn their checks.

Capability NHTSA vPIC VehDB
Data shape Raw, flat key/value VIN decode — you clean & normalise Pre-cleaned, consistent schema on every record
VIN decode Authoritative government VIN decoder Built on vPIC decoding — not a replacement authority
EPA fuel economy Not included mpg_combined, annual_fuel_cost, co2_gpm, range — inline on cars
Recalls & safety Separate NHTSA endpoints, unjoined Live NHTSA recalls + NCAP ratings, joined on the same UUID
Tire fitment Not included OEM & alternate tire sizes cross-referenced per vehicle
Powersports & marine Limited beyond on-road VINs Cleaned specs for motorcycles & power boats too
MCP / AI-native No MCP server MCP server so AI agents query the data natively
Support & SLA Best-effort public service, no SLA SLA, support and versioned endpoints
Pricing Free Free tier, then paid plans for volume

We do not provide raw per-VIN history, ownership records, or exterior L×W×H dimensions. For raw VIN authority, vPIC is the source — including for us.

Which should you use?

No single right answer — it depends on what you are building.

Use NHTSA vPIC when…

  • You need the authoritative, free VIN decode
  • You are happy to normalise raw output yourself
  • You do not need economy, recalls or fitment joined
  • Budget is zero and no SLA is required

Use VehDB when…

  • You want a clean, consistent schema out of the box
  • You need EPA economy, recalls, NCAP & tire fitment joined
  • You cover motorcycles and boats, not just cars
  • You want an MCP server, support and an SLA

See data sources, the API overview, or the MCP server.

vPIC comparison FAQ

Straight answers, including when to skip us.

Yes — vPIC is free, public and authoritative for VIN decoding, and for many projects it is the right answer. Use vPIC directly when you need raw, government-sourced decode results and are comfortable normalising the data yourself. VehDB is for teams that want that data pre-cleaned into a consistent schema and pre-joined with EPA economy, recalls, NCAP and tire fitment.
VehDB serves cleaned specs for cars, motorcycles, boats and tire sizes, and pre-joins EPA fuel economy, live NHTSA recalls, NCAP ratings and tire fitment to each record on a single UUID. It adds pagination, filtering, an SLA with support, and an MCP server so AI agents can query the data natively.
No. vPIC remains the authoritative VIN decode source and is unmatched as a free government service for that job. VehDB is best thought of as vPIC cleaned and enriched for production — a consistent schema with economy, safety and fitment data attached — rather than a replacement for the raw VIN authority.
VehDB does not provide raw per-VIN history, ownership records, or exterior L×W×H dimensions. What it adds is breadth and joins: pre-cleaned specs across cars, motorcycles and boats, tire fitment geometry, EPA economy on cars, and live NHTSA recalls and NCAP ratings — all queryable together on one UUID and exposed over MCP.

vPIC, cleaned and enriched, for production.

Build on 562 cars, 341 motorcycles and 308 boats — EPA economy, live recalls, NCAP and tire fitment pre-joined on one UUID, plus an MCP server. Free tier, no card.

Create free account Try the playground

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