Decode a Vehicle Identification Number (VIN) using the NHTSA vPIC API to populate an auto insurance quote
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
Call the NHTSA vPIC REST endpoint GET /vehicles/DecodeVinValuesExtended/{VIN}?format=json, replacing {VIN} with the 17-character VIN; the API is free, requires no API key, and is available 24/7
Parse the Results array in the JSON response; key fields include Make, Model, ModelYear, VehicleType, BodyClass, EngineCylinders, DisplacementCC, and DriveType
Validate the returned ModelYear against the year provided by the applicant; mismatches may indicate a transcription error in the VIN
Use VehicleType and BodyClass to map the vehicle to your rating tier (e.g., passenger car vs. truck vs. motorcycle) and check GVWR for commercial vehicle thresholds
Store the decoded vehicle attributes in the quote record; re-decode at policy bind to confirm the VIN has not been altered between quote and bind
Known gotchas
The vPIC API is authoritative for model years 1981 and forward only; vehicles with pre-1981 VINs will return incomplete or no data and require manual lookup
Decoded results reflect the manufacturer's reported specifications, not aftermarket modifications; a vehicle with engine or body modifications may differ materially from vPIC data
The batch decode endpoint accepts up to 50 VINs per request (semicolon-delimited string); use it for quoting pipelines processing multiple vehicles to reduce latency
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?