Vehicle data,
from your terminal.
The vehdb CLI puts 1,342,720 vehicle
records one command away — search, pipe JSON into jq, export CSV,
script bulk lookups. The REST API and MCP server are live today; the CLI is in early access.
Scripting today? The REST API works from curl right now — see below.
# planned developer experience $ vehdb login $ vehdb cars search --make Toyota --year 2026 → 14 results $ vehdb cars get a1b2c3 --json | jq .mpg_combined $ vehdb tires for a1b2c3 → OEM 235/45R18 · +2 alternates $ vehdb cars search --body SUV --export csv > suvs.csv
Built for scripts and pipelines
Everything the API does, one command away — composable with the Unix tools you already use.
Search & filter
Query cars, motorcycles, boats and tire sizes by make, model, year, body, fuel and drivetrain — straight from the shell.
JSON or CSV out
Pipe JSON into jq, or --export csv for spreadsheets and bulk jobs. Scriptable, composable, automatable.
Same data as the API
EPA economy, NHTSA recalls and tire fitment — the exact surface as the REST API and MCP server, one token.
Scripting now? Use curl
The REST API gives you the same thing from any shell, today.
curl -s "https://api.vehdb.com/v1/cars?make=Toyota&year=2026" \ -H "Authorization: Bearer YOUR_TOKEN" | jq '.data[0]'
Grab a free token in the dashboard · full reference in the API docs · or browse the SDKs.
Command reference
The planned surface — every dataset and enrichment, one verb at a time.
| Command | What it does |
|---|---|
vehdb login |
Store your API token in the local config (or use VEHDB_TOKEN). |
vehdb cars search --make Toyota --year 2026 |
Search cars by make, model, year, body, fuel and drivetrain. |
vehdb cars get <uuid> |
Full spec sheet for one car, including EPA economy fields. |
vehdb cars recalls <uuid> |
Live NHTSA recall campaigns and NCAP safety rating. |
vehdb tires for <uuid> |
OEM and alternate tire sizes that fit a vehicle. |
vehdb motorcycles search / boats search |
The same search surface for motorcycles and power boats. |
vehdb lists |
Read your saved vehicle lists. |
vehdb <cmd> --export csv |
Stream any result set to CSV for spreadsheets and bulk jobs. |
Output as --json (default), --csv or a human --table.
Recipes
Composable with the tools you already script in.
# every EV SUV's combined MPG vehdb cars search --body SUV --ev-only --json | jq '.[].mpg_combined' # bulk-decode a column of VINs/UUIDs from a file cat uuids.txt | xargs -I{} vehdb cars get {} --csv >> specs.csv # open recalls for everything in your list vehdb lists --json | jq -r '.[].uuid' | xargs -I{} vehdb cars recalls {} # in CI — fail if a model gained a new recall vehdb cars recalls $UUID --json | jq -e '.open_recalls == 0'
CLI, API or MCP?
One dataset, three front doors — pick per task.
CLI
For humans and shell scripts — quick lookups, CSV exports, cron jobs, CI checks.
REST API
For your application code — typed JSON over HTTPS, filtering, pagination, the same data.
MCP server
For AI agents — Claude, Cursor and copilots query vehicle data as native tools.
Building an app? See the SDKs and REST API. Wiring up an agent? The MCP server is live now.