Make and model data for car classifieds

Your business lives on two forms: the one sellers fill in to post an ad, and the filters buyers use to find it. Both depend on the same thing, a clean make and model on every listing. When the seller types it freely, you get "VW", "Volkswagen" and "Volkswagon" as three makes, search misses a third of the Golfs, and your model pages ("used Volkswagen Golf in Kraków") never get the listings they should.

VehiclesDB is the make and model list for that job, built for the country you operate in.

What you get

The cars your sellers actually own. The list comes from the national vehicle registers of these countries, not from a US catalogue, so a Spanish marketplace sees the SEAT Ibiza and a German one sees the VW Golf near the top.
Popularity per country, measured from registration counts, to order your make filter and your post-an-ad picker so the common cars are one tap away.
Cars, motorcycles, mopeds, vans, trucks and buses in one list with one id scheme, so your motorbike and commercial-vehicle sections use the same source as your cars: a Yamaha MT-07, a Ford Transit and a Scania R Series all have the same shape.
Body types for cars (hatchback, sedan, SUV, pickup, van…) for your body filter, and the years each model is on record for your year range.
Aliases, so "Rabbit" still finds the Golf and a seller's spelling lands on the right model.
Stable ids. Every model has a canonical id like car/volkswagen/golf; when a model is renamed or merged, the old id stays in former_ids, so listings you tagged last year still resolve.

Three ways to plug it in

The picker on your post-an-ad form. The make and model dropdown is one script tag, searchable, with logos and an Other / not listed option. Its requests cost 0 credits.
The list in your own database. Get it as CSV, JSON, Parquet or SQLite, free with an account, load it, and drive your filters and model pages from your own tables. Pin a release, update when you choose.
Clean the listings you already have. The resolve endpoint in the car API takes a messy title or an old catalogue value and returns a canonical id with a confidence score and the reason it matched, so you can normalise your whole archive in batches.

The licence, in one paragraph

The make and model list is CC-BY 4.0. You may store it, display it on public pages, build search and SEO pages on it and use it commercially, as long as you show a visible credit ("Vehicle data by VehiclesDB"). None of that costs anything. If you'd rather not show the credit, a paid plan drops it for one business: see pricing. If you need written terms for redistribution across several sites or countries, tell us what you need.

What we don't have yet

Buyers search by generation ("Golf 7", "E90") and by engine and trim, and today we don't publish those. They are the most requested addition and they're on the roadmap; if your marketplace needs them, tell us and we'll put you on the list for the first release. We also don't do VIN decoding, valuations or price guides; the provider comparison lists who does.

Staying current

Releases are versioned and usually monthly. Each one ships with a changelog of added, renamed and retired models, and every retired id points to the model that replaced it. New cars appear in the registers as they're sold; the hosted picker and API pick them up on their own, and a downloaded copy catches up when you load the next release.

Questions people ask

Can I store and display the make and model list on my marketplace?

Yes. The list is licensed CC-BY 4.0: you may store it, display it on public pages and use it commercially, as long as you show a visible credit.

Can I use it without the credit line?

Yes, on a paid plan that drops the credit line for one business (see the pricing page). Commercial use, storage and public display are already allowed under CC-BY 4.0 with a credit; the plan does not sell you rights CC-BY already gives you.

Do you have generations, engines and trims?

Not yet. Buyers search by generation ("Golf 7") and by engine, and we know it: generations are the most requested addition and are on the roadmap. Today every model has its kind, body type for cars, years on record, the countries where it is registered and its popularity there.

How often is the list updated?

Releases are versioned and usually monthly, each with a changelog of what was added, renamed or retired. Model ids are stable: a renamed model keeps its old id in former_ids, so your existing listings keep pointing at the right model.

Can it clean the make and model on listings we already have?

Yes. The resolve endpoint maps free-text titles and old catalog values to canonical ids with a confidence score and an audit trail, so you can normalise years of listings in a batch.