vindex.vin
Become a Partner

The automotive identity atlas

Vindex.vin

One car. A different ID in every database.

Chrome, KBB, Edmunds, EVOX, and vPIC each keep their own ID for the same car. Underneath them all is one ladder — brand, model line, year, trim, build. Vindex owns it, and resolves every one of their IDs through it.

vindex.vin/{VIN} — every ID this car carries · free · no account

Identity recordresolved

2016 Toyota Camry Hybrid

  • BrandToyotavxq_w68h5mg
  • Model lineCamryvxl_nwjz915ll
  • Year2016vxv_0nf9sdwcr
  • TrimHybridvxg_1zv4btj2j
  • BuildSedan · Gasoline · 4×2vxc_3nzk40r3b
On file under a different ID at
  • Chrome
  • KBB
  • Edmunds
  • EVOX
  • vPIC
1,646,113Identities in the Vindex Atlas

01 · The fracture

Every provider homes its own key.

So the industry’s data joins by hand, or not at all.

The industry’s catalogs never shared an identifier. The same physical car is a style at one provider, a vehicle at another, a pattern at a third — each under its own ID, its own trim string, its own idea of what counts as one car. Every join between two of them is a hand-kept map, drifting on its own schedule.

  • decode → booka decoded VIN priced against a valuation book’s row — the lender’s daily join, done today by string-matching trim names
  • listing → photoa listing’s style bound to the imagery catalog’s style-and-color key — or the wrong car’s pictures
  • compliance → merchandisinga government pattern reconciled with a merchandising style — two systems, no shared key
The pairwise collapsen providers
  • pair by pairevery join is its own maintained map — n·(n−1)/2 crosswalks, each drifting on its own
  • through the laddereach provider maps once — n edges, and every pair resolves through the hub

A hub only works if somebody owns it. Vindex does.

02 · The Atlas

So Vindex issued the ladder.

Marque, lineage, vintage, guise, cut — the brand, the model line, the year, the trim, the build.

The Atlas is built clean, from public evidence — no licensed database anywhere in its ancestry. Every identity is issued once, carries the evidence that earned it, and can be audited down to the row. Even the ambiguous cases are recorded and scored, never guessed — 774,116 of them — because a catalog you can audit beats a catalog you have to believe.

Issued on evidence, or not issued.

One key grammar, ten kinds of identity

  • vxq_marque
  • vxl_lineage
  • vxv_vintage
  • vxg_guise
  • vxc_cut
  • vxm_measure
  • vxf_fitment
  • vxe_ensemble
  • vxw_colorway
  • vxb_brief
One car, down the ladder2016 Toyota Camry
  1. lineagevxl_nwjz915llToyota Camry
  2. vintagevxv_0nf9sdwcr2016
  3. guisevxg_1zv4btj2jHybrid
  4. guisevxg_0jf96rbcdfactory codes ASV50L / GSV50L / AVV50L
  5. cutvxc_3nzk40r3bSedan · Gasoline · 4×2

03 · Counted

1,646,113 nodes.

Counted from the ledger, never claimed — and the ladder widens as it descends.

  1. vxq_marquethe make, curated12,240
  2. vxl_lineagethe model line, across years31,608
  3. vxv_vintagethe model year of a lineage477,156
  4. vxg_guisethe series or trim a year wears501,488
  5. vxc_cutbody · fuel · drive — the build623,621

Live counts, straight from the database

1,602,265Connections between identities
1,022,501Readable addresses registered
774,116Candidate builds recorded and scored
1,515Decisions ruled by hand

04 · The crosswalk

Any ID in. Any ID out.

Every provider’s identifier, an edge on the ladder.

A provider’s ID stays the provider’s — Vindex never rewrites it. It links to the ladder as an equivalence: this ID, this identity, this confidence, verified on this date. 43,941 links are live today, built from the federal registry; Chrome, KBB, Edmunds, and EVOX join the same way as their licenses clear.

Neutral by construction: every pair resolves through the same ladder, in either direction.

Pair resolutionvindex.vin/JM3KFBXY1S0597748
  • ina VIN — or provider:id
  • targetany mapped provider — either direction
  • outthe mapped identifier · confidence · verified timestamp

The same resolution runs as API and MCP through apis.vin — one answer for people and agents alike.

05 · Posted

The price is on the page.

For people, and for the agents they send.

The price vindex.vin

  • Freethe ladder · the counts · the coverage tables$0
  • Per resolutionone identifier in, one out, scoredposts live
  • Pair tableone provider pair’s full mapping, licensedposts live
  • Full mapthe whole crosswalk, at portfolio scalepriced on paper

Provider-mapped IDs go on sale as each provider’s license clears; the ladder and its counts stay free.

Where it’s sold data.vin · apis.vin

The Atlas is a catalog product: coverage, license, and price post at data.vin. Integration — key, SDK, quota, MCP — lives at apis.vin. vindex.vin owns the ladder and its resolution.

Every paid resolution returns a machine-readable offer — posted amount, x402 settlement, expiry — so an agent settles per call on its own account. An agent buying resolution reads this same page.

One account, every address: auth.vin.

The rest of the record

For the agent you send

The agent reads the same record you do. Same two routes, three representations — the numbers never differ between them.

motions: B2A

curl https://vindex.vin/ -H 'accept: text/markdown'        → the markdown twin of this page
curl https://vindex.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://vindex.vin/{VIN} -H 'accept: text/markdown'    → the record's markdown twin

Machine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one MCP server for the whole platform — apis.vin/mcp (every door a lens; tool results carry the door URL).

Attribution: X-Client-Type: html | md | json | mcp — read for agent-led demand attribution; it never changes the record.