NHTSA vPIC VIN Decoder API
Free US government API for decoding Vehicle Identification Numbers (VINs) into structured vehicle attributes including make, model, year, engine, trim, body type, and manufacturer details.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS enforced. No auth required — no credential surface area. Data is public vehicle specification information with no confidentiality concerns. No secret management burden for agents.
⚡ Reliability
Best When
An agent receives a raw VIN (from a form, scan, or database) and needs to resolve it to structured vehicle attributes without any API costs or signup friction.
Avoid When
You need pricing, recalls, or non-US vehicle data, or require a commercial SLA.
Use Cases
- • Decoding a 17-character VIN to retrieve make, model, year, and trim details
- • Batch decoding up to 50 VINs per request for fleet or inventory processing
- • Validating VIN format and check digit before downstream processing
- • Extracting engine displacement, fuel type, and transmission type from VIN
- • Mapping manufacturer codes to vehicle attributes for insurance or registration workflows
Not For
- • Pricing or market value data — this API is spec-only
- • Recall or safety rating data (use the NHTSA Safety API instead)
- • Non-standard VINs or vehicles pre-dating the 1981 standardized VIN format
- • Real-time vehicle status or ownership history
Interface
Authentication
No authentication required. Fully open public government API. No registration, no API key, no rate limits documented. Format parameter controls JSON vs XML output.
Pricing
Completely free. Part of NHTSA's vPIC (Vehicle Product Information Catalog) system. Batch decoding is a standout feature for bulk workflows.
Agent Metadata
Known Gotchas
- ⚠ Always returns HTTP 200 — agents must check Results[0].ErrorCode, not HTTP status, to detect decode failures
- ⚠ Partial decodes are common for older or non-standard VINs; inspect individual field confidence where available
- ⚠ Batch endpoint (POST /DecodeVINValuesBatch) accepts VINs as semicolon-delimited string in request body, not JSON array
- ⚠ Results include many null/empty fields for non-applicable attributes; agents should filter before passing downstream
- ⚠ No OpenAPI spec available — schema must be inferred from example responses
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for NHTSA vPIC VIN Decoder API.
Scores are editorial opinions as of 2026-03-06.