Datadory notebook
How Developers Builders Use Automobile Manufacturers Data: Dataset Structure and Field Coverage
Datadory delivers how developers builders use automobile manufacturers data covering comprehensive field definitions, entity mappings, and historical time series — structured for direct analytics and delivered on demand.
1,744 datasets. Pick your catch.
How do you load vehicle specifications in bulk instead?
For anything location-aware, Washington State Electric Vehicle Population Data is one of the easiest real datasets in the catalog to build on: 294,193 registered BEV and PHEV records as of August 2026, refreshed weekly on Socrata under commercial delivery terms, geocoded from county down to census tract and exported as CSV, JSON, XML, GeoJSON, KML or KMZ. At the opposite end of the size curve sit the teaching sets - the UCI Automobile Dataset's 205 instances x 26 attributes arrive as a 25.3 KB file inside an 8.3 KB ZIP, and the Kaggle mirror ships the same 205 rows as a single 4,991-byte CSV backed by 229 community notebooks for quick demo scaffolding.
What does a working VIN-decoding integration look like end to end?
The same pattern extends to EV analytics by joining decoded makes against the weekly Washington registry, which carries manufacturer and electric-range columns per registered vehicle.
Which production and registration feeds justify building a parser?
Europe's benchmark numbers live in PDFs. The two ACEA sources (both quality score 9) publish monthly passenger-car releases covering about 30 markets by country, power source and roughly 20 manufacturer groups with 40+ brands - but they arrive as six-page PDFs under ACEA copyright, where quoting with attribution is permitted and reproduction beyond that needs written consent. If your product needs a feed rather than a document, substitute Eurostat Industrial Production Index for Motor Vehicles (STS_INPR_M): monthly NACE C29 values across 42 reporting areas served as JSON, TSV or SDMX through the free dissemination API, reusable commercially under commercial delivery terms 4.0 with source acknowledgment, with data served through June 2026 at time of review.
Pick up where this leaves off
Every one of these ships with sample rows before you commit to anything.
NHTSA vPIC Vehicle Manufacturer and VIN API Data
EPA FuelEconomy.gov Web Services API Data
EPA Fuel Economy Dataset (1984-2026)
Washington State Electric Vehicle Population Data
Eurostat Industrial Production Index for Motor Vehicles (STS_INPR_M)
OICA World Motor Vehicle Production Statistics
Want rows instead of a pitch? Name the datasets.
API, files, or your warehouse. Daily, weekly, or hourly.
Get a sampleQuestions worth asking
Is there a free VIN decoder API for automobile manufacturer data?
Yes. NHTSA's vPIC API requires no integration key and returns JSON, XML or CSV. DecodeVinValues expands a VIN into up to 154 fields, and GetAllManufacturers pages 100 manufacturers at a time across 1,000+ pages of records drawn from mandatory 49 CFR Part 565 filings, refreshing monthly.
Can I pull European car registration figures programmatically?
Not directly from ACEA, whose monthly releases covering about 30 markets and roughly 20 manufacturer groups ship as copyrighted PDFs. The machine-readable route is Eurostat's STS_INPR_M service, which serves monthly NACE C29 production indices for 42 reporting areas as JSON, TSV or SDMX under commercial delivery terms 4.0.
Which automobile datasets can I reuse commercially?
Eurostat's STS_INPR_M permits commercial reuse under commercial delivery terms 4.0 with source acknowledgment, and US Government work such as vPIC and the EPA files is free to build on. ACEA and OICA allow quoting with attribution but restrict reproduction, Washington's EV data carries commercial delivery terms share-alike, and the AutoCare ACES/PIES portal is subscription-only.