Retrieve original vehicle dimensions for collision reconstruction using NHTSA vPIC's Canadian Vehicle Specifications (CVS) dataset
domain: vpic.nhtsa.dot.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the model year and make you need dimensional data for, since CVS is queried per year rather than by VIN
Call vehicles/GetCanadianVehicleSpecifications/?year={YEAR}&make={MAKE}&format=json (or format=csv) to retrieve the matching records
Optionally narrow further with model and units (metric/inches) parameters if supported for that year's dataset
Parse dimensional fields such as wheelbase, track width, and curb weight from the response for use in reconstruction or safety-engineering calculations
Cross-reference the vehicle's VIN-decoded make/model/year via DecodeVin first, since CVS lookups require exact make/model text matches
Known gotchas
CVS is a distinct dataset compiled annually by Transport Canada, not a byproduct of the standard VIN decode, and coverage/fields vary year to year
Make/model spelling must match CVS's own naming conventions, which don't always align exactly with vPIC's decoded make/model text, so fuzzy-match or offer a picker
Not every model year or every make has CVS data available; absence of a record is not evidence the vehicle doesn't exist
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?