The complete guide · 1,342,720 records · 461 makes

Vehicle data for business: the complete B2B guide.

What vehicle data is, who buys it, its types, how it is delivered, what it is used for, and how to evaluate a provider — everything a B2B or enterprise team needs to put authoritative vehicle data to work.

What vehicle data is — and who buys it

Vehicle data is structured information about vehicles: their specifications, what they cost to run, whether they are safe, and what fits them. For a business, it becomes useful when it is clean, cross-referenced and queryable at scale — not scattered across PDFs and government portals.

The buyers are teams that make decisions about vehicles by the thousand: insurers and lenders pricing risk, fleet operators tracking running costs, dealers enriching listings, fintechs decoding collateral, marketers segmenting audiences, and parts and aftermarket sellers matching fitment. VehDB serves 1,342,720 records — 853,870 cars, 233,450 motorcycles, 84,300 boats and 171,100 tire sizes — from 461 makes, with EPA economy on ~76,416 cars and live NHTSA recalls.

The four types of vehicle data

VehDB cross-references all four on one UUID per vehicle.

Specifications

Make, model, year, trim, engine, body, fuel type and drivetrain — the identity of the vehicle. Explore the Vehicle Specs API.

Fuel economy & emissions

EPA MPG, annual fuel cost, CO₂ grams/mile and EV range. See the Fuel Economy API.

Safety: recalls & NCAP

Live NHTSA recall campaigns and crash-test ratings. See the Vehicle Recalls API.

Fitment: tire sizes

OEM and alternate tire sizes with computed geometry. See the Tire Sizes API.

API vs database vs MCP

Three delivery models — VehDB offers all three.

REST API

Live, on-demand queries with filtering and pagination — best when you need today's recalls and per-request lookups.

Database / CSV

Bulk snapshot for offline joins and warehousing. Compare the trade-offs in API vs CSV database.

MCP server

Native tools for AI agents like Claude. See the vehicle data MCP server.

Vehicle data by dataset

Every dataset has its own endpoint and reference page.

Vehicle Specs API Make, model, year, engine, body, drivetrain.
Vehicle Recalls API Live NHTSA recall campaigns and NCAP ratings.
Fuel Economy API EPA MPG, annual fuel cost, CO₂ and EV range.
Commercial Vehicle API Data for commercial and work vehicles.
Cars & specs API The full car catalog with enrichment on one UUID.
Tire Sizes API OEM and alternate tire sizes with geometry.

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

How to evaluate a vehicle data provider

Five questions separate a usable provider from a liability:

  • Provenance — does it trace to authoritative sources, with no PII or DPPA exposure? See our data sources.
  • Freshness — are recalls read live, or is it a stale snapshot?
  • Cross-referencing — does one ID link specs, economy, safety and fitment, or do you join it yourself?
  • Coverage — does it span the vehicle types and years you serve?
  • Delivery — API, bulk and MCP, so it fits your stack?

Worth a direct comparison: raw government feeds are free but unjoined. See VehDB vs NHTSA vPIC for why cleaned, cross-referenced data beats decoding vPIC yourself.

Reference

New to the terminology?

VIN, vPIC, NCAP, BEV, OEM fitment, CO₂ grams/mile — the vehicle data vocabulary, defined in plain English in our glossary.

Open the glossary

Getting started

From sign-up to your first answer in three steps.

1 · Sign up free

Create an account

The free tier is real — 100 calls/mo, no card. Grab a Bearer token in the dashboard.

2 · Pick a delivery

API, bulk or MCP

Query the REST API, pull a snapshot, or wire up the MCP server.

3 · Ship it

Build your use case

Start from a solution or try the playground first.

Need more than self-serve?

Enterprise agreements are for teams that need contractual guarantees, higher ceilings, or the dataset itself.

  • Custom API quotas and rate limits beyond the Developer plan
  • Bulk data licensing — periodic dataset exports under contract
  • Invoice billing with EU VAT handling (reverse charge supported)
  • Priority support with a named contact and SLA
Contact sales
Why teams pick VehDB
EU-based & GDPR-native
Operated by Savas OÜ (Tallinn, Estonia). Your procurement team will find the paperwork familiar.
Clean data licensing
Enrichment comes from U.S. federal public-domain sources (EPA, NHTSA) — no third-party lock-in clauses.
No per-seat pricing
Plans are quota-based. Your whole team shares the workspace; your systems share the API.
Three interfaces, one record
The UUID your analyst sees in the dashboard is the UUID your backend queries and your AI agent cites.

Plans that scale with usage, not seats

Every plan includes the dashboard, the REST API and the MCP server: same token, same quota.

Free

$0
100 API calls/mo · 10/min
Start free
Most Popular

Pro

$19.99/mo
10,000 API calls/mo · 60/min
Start with Pro

Developer

$99.00/mo
100,000 API calls/mo · 300/min
Start with Developer

Enterprise

Custom
250,000+ API calls/mo · 600/min
Contact sales

Full plan comparison and FAQ on the pricing page. Prices in USD, cancel anytime.

Vehicle data for business FAQ

The questions B2B and enterprise teams ask first.

Vehicle data for business is structured information about vehicles — specifications, fuel economy, safety/recalls and tire fitment — delivered in a form teams can query at scale. B2B and enterprise buyers in insurance, fleet, dealers, fintech, marketing, parts/aftermarket and compliance use it to price risk, decode vehicles, build catalogs and ground their products in authoritative data. VehDB covers 1,342,720 records across cars, motorcycles, boats and tire sizes.
The main types are specifications (make, model, year, engine, body, drivetrain), fuel economy and emissions (MPG, CO₂, EV range), safety data (recalls and NCAP crash-test ratings), and fitment data (OEM and alternate tire sizes). VehDB delivers all four cross-referenced on one UUID per vehicle.
Three ways. A REST API for live, on-demand queries; a CSV/database snapshot for bulk and offline use; and an MCP (Model Context Protocol) server so AI agents can query vehicle data natively. VehDB offers all three so you can pick the delivery model that fits your stack.
Check provenance (authoritative sources, no PII/DPPA exposure), coverage, freshness (live recalls vs stale snapshots), cross-referencing (one ID linking specs, economy, safety and fitment), and delivery options (API, bulk, MCP). VehDB publishes its data sources and offers a free tier so you can evaluate before committing.
AI-NATIVE · MCP SERVER

Your AI agent's vehicle-data tools —not glue code.

VehDB ships a native Model Context Protocol server. Claude, Cursor or any MCP client queries cars, recalls, fuel economy and tire fitment as first-class tools — no wrappers, no scraping, no glue code to maintain.

  • Native MCP tools — search_vehicles, recalls_for_vehicle, complaints_for_vehicle, tire_sizes_for_vehicle, my_lists — callable by Claude, Cursor or any agent.
  • One-click AI connector in Claude; in any other MCP client, paste one URL and sign in: no token to copy. Scripts use an API token. Same data and quota as the REST API.
  • No scraping, no function-calling boilerplate, no schema drift — the agent gets typed, documented tools.
One-click AI connectors
claude_desktop_config.json
{ "mcpServers": {
    "vehdb": { "url": "https://mcp.vehdb.com/mcp" }
  } }
# the agent calls a typed tool, not your scraper
tool search_vehicles(make="Toyota", year=2026)
tool tire_sizes_for_vehicle(uuid) → "235/65R17" …

Put 1,342,720 vehicle records to work.

Specs, EPA economy, live recalls and tire fitment across 461 makes — by API, bulk or MCP. Free tier: 100 calls/mo, no card.

100 free API calls every month · REST API + MCP server on every plan · No card to start · See pricing