Attribution

The open VehiclesDB dataset is licensed CC BY 4.0. Visible credit with a link is a condition of the license (§3(a)), not a courtesy. This page is the designated attribution form — copy the snippet that fits your medium and you're fully compliant.

Prefer not to show a credit, or need the enriched paid layer? That's the commercial license — it waives only our credit; the upstream register notices in the dataset's ATTRIBUTION file apply under every license (they are the registers' own terms, not ours to waive).

Website (HTML)

<a href="https://vehiclesdb.com">Vehicle data by VehiclesDB</a>

Even better: link the page you actually used. Deep links help your readers land on the exact vehicle, and help us more than a homepage link:

Data: <a href="https://vehiclesdb.com/cars/seat/leon">SEAT León — VehiclesDB</a>

Markdown (READMEs, docs, blogs)

Vehicle data by [VehiclesDB](https://vehiclesdb.com) (CC BY 4.0)

README badge

[![Vehicle data: VehiclesDB](https://img.shields.io/badge/vehicle%20data-VehiclesDB-blue)](https://vehiclesdb.com)

Research, academia & journalism

Always cite the dataset version you used — it's in manifest.json of every release (e.g. 2026.08.1). The GitHub repository also carries a CITATION.cff, so GitHub's "Cite this repository" button produces both formats below.

APA (7th ed.):

VehiclesDB. (2026). VehiclesDB: The open source vehicle database (Version 2026.08.1) [Data set]. Zenodo. https://doi.org/10.5281/zenodo.21744943

BibTeX:

@misc{vehiclesdb,
  title        = {{VehiclesDB}: the open source vehicle database},
  author       = {{VehiclesDB}},
  year         = {2026},
  howpublished = {\url{https://github.com/vehiclesdb/vehiclesdb}},
  doi          = {10.5281/zenodo.21744943},
  note         = {Open dataset, CC BY 4.0, version 2026.08.1}
}

In prose (journalism, books): "according to VehiclesDB (vehiclesdb.com), the open source vehicle database" — with a link where the medium supports one.

Apps and anything without a website

Name us visibly in the app description or an about/credits screen:

Vehicle data by VehiclesDB (vehiclesdb.com)

API consumers

Attribution is required on every plan wherever API-derived data is publicly displayed, in the form above — unless your Plan or a signed agreement expressly includes an attribution waiver (typically upper tiers and enterprise contracts). See the Terms of Service §10.3 and API Terms §4.

API responses carry a machine-readable attribution object (source, url, license, dataset_version). Keep it intact when you store or pass data onward: if you are licensed to serve our data through your own API or product, each response or record containing our data (or data derived from it) must include those fields and, where displayed, the visible link.

---

Questions, edge cases, or a medium not covered here? [email protected].