# vindex.vin
> One YMMTS spine — year, make, model, trim, style — with every industry data provider's IDs and trim, style, color, and option codes cross-mapped between all of them.

Vindex is the Rosetta Stone of automotive industry data: the same vehicle carries a different identifier at every provider — Chrome, KBB, Edmunds, EVOX, vPIC, and the rest. Vindex maps them to one YMMTS spine and to each other, with coverage posted per provider pair.

Motions: B2A
Routes: GET / (this document's page) · GET /{VIN} (the record for one vehicle)
Representations: text/html · text/markdown · application/json (Accept header; same URL)
Evidence: every field posts value · source · timestamp · verification state; empty states are typed EMPTY, invalid VINs are typed INVALID_VIN — never a faked 200.
Agent surface: one estate MCP server — https://apis.vin/mcp (all .vin doors are lenses over one spine; tools: decode_vin, vehicle_history, market_value, window_sticker, out_the_door_price, open_recalls, search_listings, cash_offer, transport_quote, finance_prequal, insurance_quote, start_purchase)
Gates: typed OFFER (posted price, hard ceiling, x402) or NEEDS_HUMAN handoff URL — no account walls.
Auth: https://auth.vin (issuer) · keys/metering via id.org.ai
Siblings:
https://data.vin/ — The pillar door: the crosswalk is a catalog product — coverage, license, price, posted.
https://apis.vin/ — The HOW: one key, one MCP server — the same crosswalk, machine-read.
https://specs.vin/ — The spine's factory numbers for any VIN — dimensions, powertrain, capacities, posted.
https://build.vin/ — The as-built record for any VIN — the option codes the crosswalk maps, as the factory ordered them.
https://listings.vin/ — The live-listings spine — the decode and slug grammar the YMMTS hierarchy serves.
https://all.vin/ — Every door, one record: all.vin/