Decode a VIN for a vehicle assembled at a Canadian plant using the NHTSA vPIC API and confirm no special handling is required

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

  1. Call GET /vehicles/DecodeVinValues/{vin}?format=json against vpic.nhtsa.dot.gov exactly as for any North American VIN — there is no separate Canadian decode endpoint
  2. Check the returned Manufacturer/Make fields, since Canadian-plant WMI codes resolve to distinct manufacturer names (e.g. 'HONDA OF CANADA MFG., INC.') that differ from their US-plant counterparts
  3. If cross-referencing WMI ownership directly, use GetWMIsForManufacturer or GetManufacturerDetails, which support searching by Canadian manufacturer name strings
  4. Do not confuse this with the separate GetCanadianVehicleSpecifications endpoint, which returns Transport Canada physical dimension data (by make/model/year, not by VIN) for collision-reconstruction use cases
  5. Validate the response's ErrorCode/ErrorText fields since a Canadian-built VIN can still trip a check-digit or unrecognized-WMI error independent of its origin

Known gotchas

Related routes

Decode a VIN using the NHTSA vPIC API
vpic.nhtsa.dot.gov · 5 steps · unrated
Decode VINs with the NHTSA vPIC API
vpic.nhtsa.dot.gov · 6 steps · unrated
Decode a Vehicle Identification Number (VIN) using the NHTSA vPIC API to populate an auto insurance quote
vpic.nhtsa.dot.gov · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans