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.
The coverage manifest at data.vin/{VIN}: free · every VIN · no account
2025 Mazda CX-5
- World manufacturerJM3Mazda
- Vehicle attributesKFBXYCX-5
- Check digit1Verified
- Model yearS2025
- Plant0Assembly plant code
- Serial597748Production sequence
- data.vin/JM3KFBXY1S0597748The coverage manifest: which datasets hold rows, quoted as one typed bundle
- vhr.vin/JM3KFBXY1S0597748What happened to it: the full history record
- values.vin/JM3KFBXY1S0597748What it is worth: five numbers, each with its basis
- listings.vin/JM3KFBXY1S0597748Is it for sale: the live-listing corpus
- sticker.vin/JM3KFBXY1S0597748The original window sticker, as printed
- recalls.vin/JM3KFBXY1S0597748Open campaigns and remedy status
- specs.vin/JM3KFBXY1S0597748The factory specifications
- build.vin/JM3KFBXY1S0597748The OEM as-built record
- vindex.vin/JM3KFBXY1S0597748Every provider’s ID for this car, on one ladder
The catalog.
Seven canonical addresses.
Each dataset is a consumer product at its own address and a licensable dataset here.
- values.vinWhat it is worth: five numbers with their basis (retail, private party, trade-in, wholesale, auction).
- listings.vinIs it for sale: the live-listings spine, price, venue, days on market, and the decode-and-slug grammar.
- specs.vinThe factory specifications for the vehicle as designed.
- recalls.vinIs it safe: open campaigns and remedy status; the retention engine.
- sticker.vinHow it left the factory: the window sticker, the birth record, MSRP and factory options, as printed.
- build.vinThe OEM as-built record for one serial number.
- vhr.vinFlagshipThe full report: history, records, everything, in one paid document; owners, odometer readings, title events, each with its timestamp.
The record a consumer reads is the record a dealer prices from. Same rows, both registers.
JM3KFBXY1S0597748
2025 Mazda CX-5
- Title recordIn the record
- Odometer readingsIn the record
- Recall checkrecalls.vin
- Window stickersticker.vin
- Market valuesvalues.vin
- Five value types, figures rendered at values.vin
- RetailPosts live
- Private partyPosts live
- Trade-inPosts live
- WholesalePosts live
- AuctionPosts live
Figures render live at the address. This page states structure, not prices.
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.
- 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.
- 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
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.
- 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
- Machine surfaces/llms.txt/icp.json/.well-known/agents.json
- 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.