The record layer

One VIN opens the full record.

Every fact about every car, cataloged: seven canonical addresses, one featured crosswalk, one batch product. Posted coverage, posted license, posted price, keyed to the same seventeen characters.

2025 Mazda CX-5 · check digit 1 · verified

The coverage manifest at data.vin/{VIN}: free · every VIN · no account

The catalog.

Seven canonical addresses.

Each dataset is a consumer product at its own address and a licensable dataset here.

The Rosetta Stone of automotive industry data.

Featured: vindex.vin, the crosswalk every other row joins through.

One neutral ladder, the Vindex ladder (year, make, model, trim, style: YMMTS), with every industry provider’s IDs and trim, style, color, and option codes cross-mapped between all of them. A provider’s ID is a sameAs edge on the ladder, never a join key; every other row in this catalog joins through it.

The identity manifest, as a buyer reads itvindex.vin/{VIN}
1// 200 · every provider’s ID for one VIN, evidence-stated
2{
3 "type": "vindex.identity",
4 "vin": "JM3KFBXY1S0597748",
5 "ladder": {
6 "year": 2025, "make": "Mazda", "model": "CX-5",
7 "trim": <resolved, or candidates with scores>,
8 "style": <resolved, or candidates with scores>
9 },
10 "edges": [
11 { "provider": <provider mark>, "id": <that provider’s ID>,
12 "confidence": <posted, 0–1>, "verified": <RFC 3339> }
13 ],
14 "coverage": <posted per provider pair, per model year>
15}
Evidence
  • resolve(vin | provider:id) returns the identity manifest: every known provider ID, each edge scored.
  • Pairwise resolution: provider A’s ID to provider B’s, neutral and scored.
  • Where the VIN bottoms out at pattern level, candidates enumerate with scores, never a silent pick.
  • Coverage posted per provider pair, per model year, before purchase.

A mapping posts only once verified, with its timestamp. Confidence is a number the buyer reads, not an adjective this page uses.

The batch product.

Upload the file. The rows come back enriched.

CSV or XLSX, one VIN column. Every row returns with the VIN decoded and the record appended: year, make, model, trim, and the datasets the license names. The same capability runs as API and MCP through apis.vin.

The file goes in at enrich.vin.

Batch enrichment
  • Ininventory.csv · one VIN column
  • OutThe same file, every row appended: decode · the licensed datasets
  • ViaUpload at enrich.vin · API and MCP through apis.vin

Per-row price posts at the address: a number is posted or it is absent.

What and how.

data.vin sells the catalog. apis.vin sells the key.

The what

data.vin

Coverage · license · posted price · the x402 per-VIN bundle. The manifest at data.vin/{VIN} states which datasets hold rows and prices the full record as one typed bundle. It renders no member’s face: the readings live at the member addresses.

The bundle composes the members’ posted prices; it never undercuts a member’s gate, and a bundle containing the history report credits per vhr.vin’s posted rule: the member’s rule, restated, never re-priced.

The how

apis.vin

Key, SDK, quota, and MCP are apis.vin’s job: this page prices what it integrates. One MCP server for the whole platform: apis.vin/mcp. One account, every address: auth.vin.

Every paid action returns a typed, machine-readable offer (posted amount, x402 settlement, expiry), so the worst case is on paper before the first byte moves. An agent buying data reads this same page.

  • FreeRead the catalog · quote any VIN$0
  • StarterMetered · per-call price postedPosts live
  • GrowthMetered · volume tierPosts live
  • ScaleMetered · volume tierPosts live
  • Bulk / firehoseDataset licensing at portfolio scalePriced on paper

Bundles settle when the gate clears · upstream data license must name catalog resale and the x402 bundle envelope (incl. section slicing) before any per-VIN bundle transacts

Catalog reads and coverage manifests stay free.

For the agent you send.

The agent reads the same record you do.

Same two routes, three representations: the numbers never differ between them.

Three representationsdata.vin
1curl https://data.vin/ -H 'accept: text/markdown'
2 # the markdown twin of this page
3curl https://data.vin/{VIN} -H 'accept: application/json'
4 # the record as typed evidence objects
5curl https://data.vin/{VIN} -H 'accept: text/markdown'
6 # the record's markdown twin
On this host
  • Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the callb2a2dThe capability embeds downstream: reserved acts route back to a credentialed human leaf
  • One MCP serverapis.vin/mcp serves the whole platform: every door’s tools in one server, each result carrying its door’s URL.
  • AttributionX-Client-Type: html | md | json | mcp names which reader arrived; it never changes the record.