VIN Decoder: Open Safety Investigations & Recalls
Pricing
from $2.00 / 1,000 results
VIN Decoder: Open Safety Investigations & Recalls
Decodes VINs and checks each vehicle against NHTSA's recall campaigns and its open defect investigations - the ones that have not produced a recall yet, and which a recall search therefore reports as nothing at all. Says plainly what is model-level and what is not.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Ai-Q Labs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
A recall is the end of a process. Before it there is an investigation — NHTSA has opened a file on a suspected defect and has not yet decided.
Every VIN tool answers "any recalls?". None of them answers "is this model under investigation right now?" — and that is the question a recall search silently returns no to.
The problem, with real examples
Run a recall check on a 2013 Honda Odyssey today and you learn nothing about DP26005, Inadvertent Deployment of Air Bags, opened 13 July 2026 and still open with no recall issued.
A 2018 Tesla Model 3 has several open investigations and no recall for any of them, including FSD Collisions in Reduced Roadway Visibility Conditions and Sudden Unintended Acceleration.
A 2014 Range Rover has EA26003, Front Steering Knuckle Fractures, open since April 2026. A 2022 Rivian R1T has PE26004, Rear Toe Link May Separate.
All four report clean on a recall-only check.
What this Actor does
For each VIN it decodes the vehicle and then reconciles four NHTSA sources:
| Source | What it answers |
|---|---|
| vPIC | What the vehicle is — make, model, year, body, engine, plant, driver-assistance systems |
| Recalls API | Which recall campaigns cover this make, model and year |
| ODI investigation history | Which defect investigations are open, and whether any produced a recall |
| Complaints & NCAP | Owner complaint volume by component, and crash test ratings |
No API key is needed for any of them, and nothing is scraped.
The checks
| Code | Severity | What it means |
|---|---|---|
open_investigation_no_recall | high | NHTSA is investigating a suspected defect on this model year and no recall exists. A recall search reports nothing here. |
open_investigation_with_recall | medium | An open investigation that has already produced campaigns. Open means the agency has not finished. |
recall_campaigns_for_model_year | medium | Campaigns cover this model year — see the honesty note below. |
check_digit_failed | medium | The VIN fails its own check digit. Almost always a transcription error. |
model_year_mismatch | medium | Position 10 of the VIN and NHTSA's decode disagree. |
open_investigation_related_variant | low | An open investigation covers a related trim rather than this exact model. |
complaint_cluster_without_action | low | Complaints concentrate on one component with no recall or investigation. This Actor's inference, not NHTSA's finding. |
What it deliberately does not claim
It never says a recall is outstanding on your specific car. NHTSA's public API answers at make/model/year granularity; the VIN-level lookup on its website is not exposed as an API (/recalls/vin/<VIN> returns 403 — the route does not exist). A car may sit outside the affected production range, or have had the work done years ago. So the field is named recallCampaignsForModelYear, the output carries vinLevelRecallStatusAvailable: false, and the message tells you to confirm with the manufacturer. Tools that print "your VIN has 3 open recalls" from this same data are overstating it.
An open investigation is NHTSA's record; a complaint cluster is a pattern this Actor read. They get different severities and different wording.
A healthy vehicle produces no findings. If there is nothing open, nothing recalled and no unusual complaint concentration, the row comes back silent. A report where everything is flagged is a report nobody reads.
The check digit is only checked where the standard requires one. Vehicles built outside North America are not required to carry a valid one, and many do not — flagging those would put a warning on a large share of ordinary imports.
If the investigation file could not be read, the status is unknown, never clear. Absence of a finding is not evidence of absence.
Input
{"vins": ["5FNRL5H66DB000001", "5YJ3E1EAXJF006588"],"checkInvestigations": true,"includeComplaints": true}
Output
One row per VIN. The fields that carry the verdict:
| Field | Values |
|---|---|
safetyStatus | open_investigation · investigation_in_progress · recalls_to_verify · nothing_outstanding · unknown |
openInvestigationsWithoutRecall | Count of open investigations that produced no recall |
investigations[] | { investigationId, subject, component, opened, closed, isOpen, recallIssued, linkedRecallCampaigns } |
recallCampaignsForModelYear | Campaign count for the model year, not for this VIN |
issues[] | { code, severity, message, evidence } |
highestSeverity | high · medium · low · ok |
Alongside them: the full decode (make, model, year, trim, body, engine, drive, fuel, plant, GVWR, driver-assistance systems), checkDigitValid, complaintCount with crashes, fires, injuries and deaths reported, complaintTopComponents, and safetyRatings.
Three key-value records are written as well: SUMMARY, OPEN_INVESTIGATIONS (the vehicles with something open and no recall) and NEEDS_ATTENTION.
How it stays cheap
Only the decode is per-VIN. Recalls, investigations, complaints and ratings are all model-level, so a fleet of two hundred identical vans is one safety lookup, not two hundred. The investigation history is a single 2 MB download for the whole run.
Limits, stated plainly
- US market only. These are NHTSA datasets.
- Investigations are matched on make, model and model year, which is the granularity NHTSA publishes. A trim-specific defect on a variant is reported separately rather than merged.
- The investigation file is point-in-time. It is refreshed periodically; an investigation opened this week may not be in it yet.
- Of the 5,338 investigations in the file, 4,060 name a specific vehicle — the rest are equipment and tyre inquiries with the vehicle columns blank, and cannot be matched to a VIN. Within the 4,060, 118 are open and 94 have produced no recall.
- No VIN-level recall completion status exists publicly. See above.
Sources
- NHTSA vPIC —
https://vpic.nhtsa.dot.gov/api/ - NHTSA recalls, complaints and safety ratings —
https://api.nhtsa.gov/ - NHTSA ODI investigation history —
https://static.nhtsa.gov/odi/ffdd/inv/FLAT_INV.zip
This Actor reports what those sources say. It is not a safety certification, and it does not replace checking a specific VIN at nhtsa.gov/recalls before buying or dispatching a vehicle.