Decode a VIN into trim-level specs and manufacturer options packages using MarketCheck's NeoVIN Enhanced Decoder
domain: marketcheck.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a MarketCheck API key and confirm your plan includes the NeoVIN (enhanced) decoder rather than only the basic specs decoder
Call GET /v2/decode/car/neovin/{vin}/specs with your API key to retrieve enhanced trim, drivetrain, and equipment fields
Call the companion GET /v2/decode/car/neovin/{vin}/options-packages endpoint to retrieve manufacturer options packages installed on that specific VIN
Merge the two responses keyed by VIN for a full trim + installed-options profile to enrich a listing or valuation workflow
Fall back to the basic /v2/decode/car/{vin}/specs endpoint for VINs where NeoVIN returns no enhanced match, since coverage depth varies by make/model/year
Known gotchas
NeoVIN and the basic decoder are billed/rate-limited as separate products on some plans, so a naive migration from basic to NeoVIN can unexpectedly change your usage costs
Options-package data reflects what MarketCheck's data pipeline has matched for that VIN's build, not a guaranteed complete factory build sheet — treat missing packages as 'unknown' rather than 'not installed'
Older or low-volume VINs may resolve basic make/model/year successfully while returning empty trim/options fields from NeoVIN, so handle partial responses rather than assuming all-or-nothing
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?