1,342,720+ vehicle records · EPA & NHTSA enriched

One vehicle dataset. Every record an endpoint.

Cars, motorcycles, power boats and tire fitments through a single REST API — UUID-based resources, JSON responses, advanced filtering, and enrichment your team can act on: fuel economy, recalls, tire geometry.

Start free — no card required API docs

Free plan includes 100 API calls/mo — and a live playground to test queries.

api.vehdb.com
# Four datasets, one auth header
GET /v1/cars?make=Toyota&year_min=2022
{ "data": [ { "make": "Toyota", "model": "RAV4",
  "year": 2023, "mpg_combined": 30, … } ],
  "meta": { "total": 112, "per_page": 25 } }
GET /v1/motorcycles?motorcycle_type=Sport
GET /v1/boats?hull_type=Fiberglass&hp_min=200
GET /v1/tire-sizes?make=Toyota&model=Camry
# Enrichment on the same IDs
GET /v1/cars/{uuid}/recalls → NHTSA + NCAP
GET /v1/tire-sizes/{uuid}/geometry → Ø, revs/mi, ±3%

Four datasets, one API

Each vehicle type has its own endpoint group with full specifications and filtering. Same auth, same response shape.

853,870

Cars API

GET /v1/cars

Make, model, year, engine, body, fuel and drive type — plus EPA fuel economy, NHTSA recalls and tire cross-references.

Explore Cars API →
233,450

Motorcycles API

GET /v1/motorcycles

Sport, cruiser, touring, adventure and more — with type filtering, full-text search and NHTSA recall lookups.

Explore Motorcycles API →
84,300

Boats API

GET /v1/boats

Power boats with length, horsepower, hull type and fuel type — filterable by every spec.

Explore Boats API →
171,100

Tire Sizes API

GET /v1/tire-sizes

OEM and alternate sizes per vehicle, plus computed geometry with the ±3% diameter rule built in.

Explore Tire Sizes API →

Authenticate once, query everything

Bearer tokens, per-plan quotas, and a few fair-use query rules. That's the whole integration surface.

Quick start

Your first call, in one line

curl "https://api.vehdb.com/v1/cars?make=Toyota&year=2020" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"
  • Create named, read-only tokens in the dashboard — revoke anytime
  • Live usage on every response and via GET /v1/me
  • Or skip curl: the playground auto-provisions a token
  • Browse every endpoint in the interactive API reference
  • Machine-readable spec: OpenAPI 3.1 — import straight into Postman, Insomnia or your codegen
Quotas & rules

Limits by plan

Free 100/mo · 10/min
Pro 1,000/mo · 60/min
Developer 100,000/mo · 300/min
Enterprise 250,000/mo · 600/min
  • Every search needs at least one filter (make, model, year or q)
  • Up to 25 results per page, 40 pages deep per query
  • Single records by UUID: GET /v1/cars/{uuid}

Not just specs — decision-grade enrichment

U.S. government public data and computed engineering values, already joined to the record.

EPA fuel economy

Cars carry mpg_combined, annual_fuel_cost, co2_gpm and epa_range_miles — sourced from fueleconomy.gov, returned inline with the spec.

NHTSA recalls & NCAP

GET /v1/cars/{uuid}/recalls and /v1/motorcycles/{uuid}/recalls return live recall campaigns plus crash-test ratings for cars.

Computed tire geometry

GET /v1/tire-sizes/{uuid}/geometry returns diameter and revs-per-mile, with each alternate size validated against the ±3% diameter rule.

Frequently asked questions

Common questions about the VehDB Vehicle Data API.

The VehDB API provides access to 1,342,720+ vehicle records including 853,870 cars with full specifications (make, model, year, engine, body type, fuel type, drive type), 233,450 motorcycles, 84,300 power boats, and 171,100 tire size specifications with OEM and alternative sizes. This includes 57+ electric and hybrid vehicle records.
The VehDB API uses API key authentication. After registering for an account, you receive a unique API key. Include this key in the Authorization header of every request as a Bearer token. API keys can be regenerated from your dashboard at any time.
API access is included on every plan: Free 100/mo (10/min), Pro 1,000/mo (60/min), Developer 100,000/mo (300/min), Enterprise 250,000/mo (600/min). Quota usage is returned in response headers and via GET /api/v1/me.
The VehDB API returns all data in JSON format following RESTful conventions. Responses include a data array with vehicle records and a meta object containing pagination details such as total count, current page, and items per page. All vehicle resources use UUID-based identifiers for secure, non-sequential access.
API access is included on every plan — Free (100/mo), Pro ($19.99/mo, 1,000/mo), Developer ($99/mo, 100,000/mo) and Enterprise (custom) — no separate API fee. Visit the pricing page for full plan details.
The VehDB API provides four main endpoint groups: /api/v1/cars for car data with full specifications, /api/v1/motorcycles for motorcycle data, /api/v1/boats for power boat data, and /api/v1/tire-sizes for tire size specifications. Each endpoint supports GET requests for listing with filters, and GET requests with a UUID for individual vehicle details.
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, tire_sizes_for_vehicle, recalls, my_lists — callable by Claude, Cursor or any agent.
  • OAuth2 for AI providers plus simple Bearer tokens. Same auth, same data as the REST API and workspace.
  • No scraping, no function-calling boilerplate, no schema drift — the agent gets typed, documented tools.
Explore the MCP server Connect your agent
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" …

Your first API call is 3 minutes away.

Create an account, grab a token in the dashboard, query 1,342,720+ vehicle records. The free tier is real — 100 calls/mo, no card.

Create free account Try the playground

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