A structured, VIN-anchored vehicle database built for repair, diagnostics and parts matching:
Every model record is anchored by its 8-character VIN prefix and carries the complete factory parameter sheet — from body dimensions and curb weight to engine, battery, transmission, chassis and tyres. Because the record is VIN-anchored rather than name-anchored, two vehicles with identical names but different powertrains remain separate records, which eliminates the classic same-name wrong-part problem.
Three entry points cover every workflow: browse the brand matrix, narrow with the top filter bar, or paste a full 17-digit VIN to jump straight to the matching record. For example, pasting a Camry VIN skips six manual filtering steps and lands on the exact parameter sheet in seconds.
Every brand and series also has a static landing page (e.g. /brand/toyota/, /brand/toyota/camry.html) — fast to crawl, friendly to search engines.
The filter bar and the VIN box work together: filter first when you already know the vehicle, decode first when you only have the VIN — both paths land on the same parameter sheet, so a workshop can mix the two habits freely.
The database uses a fixed five-level hierarchy — Brand, Series, Year, Model and Fuel — so a query like "2021 Toyota RAV4 Hybrid" resolves to exactly one record. In addition, each level has its own static page with human-readable URLs, which means the hierarchy doubles as a site map that both users and search engines can crawl. Each record also has one canonical URL even though it is reachable from the brand matrix, the filter bar and the VIN decoder, so link equity stays concentrated for search engines.
| Level | Example | Count |
|---|---|---|
| Brand | Toyota | 549 |
| Series | Toyota Camry | 4,365 |
| Model version | Camry 2.5G (2021, hybrid) | 66,619 |
Coverage spans mass-market brands, premium marques, commercial vehicles and new-energy specialists, with the same five-level hierarchy applied uniformly — so a BYD record is structured exactly like a BMW record. In addition, the dataset mixes long-running nameplates with recently launched electric platforms, which is why the series count (4,365) is large relative to the brand count (549): each body-style or powertrain split becomes its own series.
| Segment | Examples in the database |
|---|---|
| Mass-market passenger | Toyota, Honda, Volkswagen, Ford, Nissan, Hyundai |
| Premium & luxury | BMW, Mercedes-Benz, Audi, Porsche, Lexus, Volvo |
| New energy | BYD, Tesla, NIO, XPeng, Li Auto, Rivian |
| Commercial & off-road | Land Rover, Jeep, Isuzu, MAN, Freightliner |
Beyond interactive browsing, the full database can be licensed for internal systems: the VIN database and the model parameter database are delivered as CSV or MySQL dumps on a scheduled basis, with normalization, translation into the 14 interface languages and quality-audit reports available as add-ons. As a result, a parts marketplace or diagnostic-tool maker can run the same records inside its own product while the public site keeps serving individual technicians.
The dataset is compiled from brand official technical publications, reviewed by the EV Manual technical content team, and refreshed on a rolling basis — the current release was updated on 2026-10-15. As a result, newly released model versions typically appear within weeks of the brand's official documentation, not months later. Older model years remain in the database permanently, so legacy vehicles are not dropped as new records arrive.
VIN decoding follows the ISO 3779 VIN standard, and every decode reports its match level so downstream systems know whether they received an exact-prefix match, a WMI fallback or brand-level candidates.