Identify the subject vehicle
Review available VIN-linked identity, body and drivetrain records beside registration documents and physical VIN checks. A decoded VIN is not proof of ownership or a forensic identity check.
VINdata.io for vehicle assessors
Assess the vehicle with its factory context in view.
Bring available factory identity, paint and option records into your assessment file. Keep source data traceable while you establish damage, repair scope and value through your own professional process.
Free trial lookupsNo credit card12 languages
Before the assessment is signed
The right configuration is a starting point.
- A broad model description may not distinguish the engine, transmission or original option configuration.
- Different lighting, glass or assistance-system versions can raise questions during repair planning.
- Paint records can support research but cannot establish the finish or colour variation on the vehicle today.
- A defensible case file needs factory records separated from observed damage, estimates and professional conclusions.
VINdata.io
A source-data layer for the assessment file
Research configuration details
Use original option descriptions to guide questions about lighting, glazing and driver-assistance components. Confirm installed components physically and through the appropriate OEM catalogue.
Check factory finish context
Where returned, use factory paint and interior records as references for research. Confirm the current finish and shade with the repairer; no paint formula or colour-match guarantee is supplied.
Support repair-scope review
Give your repairer the relevant source records when discussing version-dependent work. Obtain part numbers, repair methods, calibration requirements, labour times and costs from the appropriate technical sources.
Document specification context
Attach selected raw records to your assessment alongside dated photos and findings. If configuration is considered in your valuation, use your own market evidence; VINdata does not produce a value.
Connect case-management tools
Use an approved API to request records for your case file or a compatible MCP assistant to organise them. Keep human review and professional responsibility with your assessment team.
Verified example from saved vehicle data
See what a lookup returns
A real cached Volkswagen Passat report with 203 factory records. These selected original entries show what your team can review. This is an example, not a live lookup; coverage and available fields vary by VIN.
Volkswagen Passat · 2016
WVWZZZ3CZGE200403
Subject vehicle & drivetrain
pk8bNotchback
ptr14-cylinder diesel engine 2.0 L unit 04L.A
p7mmEmission standard EU6 plus
pg1a6-speed automatic transmission or DSG note: family EDF
Options for technical review
pka2Rear view camera system
pps4Tilting and sliding panoramic sunroof
p8t8Adaptive Cruise Control ACC "stop & go" incl. speed limiter
pzncNavigation system "Discover Pro"
Finish & specification context
p4a4Heated front and outer rear seats
pa8fHighline
pwlhLED headlamps with dynamic cornering light and LED separate daytime running light
lb7w/Tungsten Silver Metallic/Tungsten Silver Metallic
Explicit exclusions
p1d0Without trailer hitch
pks0Without head-up display
p7y0Without lane change assist
pqk0Without multifunction camera
Descriptions above are original source records in English. They are not AI-generated equipment flags. Factory lists can include technical entries, duplicates and explicit exclusions; coverage and detail vary by manufacturer and VIN.
Missing is not the same as absent
“Without trailer hitch” is an explicit factory record. An option that is simply missing from the response remains unknown. Neither case confirms the current vehicle’s configuration without inspection.
AI & integrations
Keep source records separate from professional judgement
Evaluate a few representative case VINs. Check whether the returned records answer your configuration questions before connecting case-management software.
MCP for AI assistants
Connect a compatible assistant such as Claude or ChatGPT to https://mcp.vindata.io/api/public/mcp using your approved API key. Retrieve and organise the returned factory records for human review. Do not infer missing equipment, guess a model or replace a physical inspection.
Try the MCP demoREST API
Integrate structured VIN data into your own workflow, preserving raw option codes and descriptions. API access requires approval. Free accounts have three successful lifetime trial calls in total, shared across keys, without a monthly reset or expiry date. Your developers implement the connection.
See API documentationFactory context, not a damage or valuation report
A lookup does not detect accidents, establish causation, verify repair quality, estimate labour or parts prices, calculate market value or decide an insurance claim. It does not replace physical examination, diagnostic tests, OEM repair instructions or professional judgement. Data availability varies by VIN.
Plans for vehicle assessors
Use the website for individual assessment files. For case-management integration or higher volume, discuss approved API access and an enterprise agreement. Website bulk lookup is not available to ordinary accounts.
Frequently asked questions
Does the lookup show accident damage or previous repairs?
No. This page describes factory configuration decoding, not a damage check or repair-history report. Establish damage and repair evidence through your own examination and other appropriate sources.
Can you calculate repair costs or a total-loss decision?
No. No labour times, parts pricing, market valuation or claims decision is included. Use the configuration records only as supporting context in your own assessment process.
Do option codes tell us what needs ADAS calibration?
They may guide questions about the original configuration, but they do not establish current components or calibration requirements. Verify the vehicle and follow the applicable manufacturer repair procedure.
Can the records become part of our case file?
You can use available specifications and raw records as a labelled reference in your workflow. Preserve the distinction between source data and your findings, and discuss API integration and display requirements with us.
How can we test coverage for our vehicles?
Apply for API access and test representative VINs from the makes, ages and markets you work with. Free accounts receive three successful API trial calls in total, shared across keys, with no monthly reset or expiry date. Contact support@vindata.io if your evaluation needs a larger agreed sample.