The as-built record · Data

The car, as the factory ordered it.

Options, packages, color codes, plant, and build date: the as-built data behind the window sticker, keyed to seventeen characters. Reading the build is free. No account.

2025 Mazda CX-5 · check digit 1 · verified

The build record at build.vin/{VIN}: $0 · every VIN · no account

Vehicle identification numberVINDecodes as you type
What each character says
  • World manufacturerJM3Mazda
  • Vehicle attributesKFBXYCX-5
  • Check digit1Verified
  • Model yearS2025
  • Plant0Assembly plant code
  • Serial597748Production sequence
The build recordAs the factory ordered it
  • IdentityYear · make · model · trim · body style
  • BuildPlant · build date · port of entry, where the record states them
  • ColorsExterior color code · interior color code
  • PowertrainEngine · transmission · drivetrain, as ordered
  • Options & packagesAs ordered, counted here; named and priced at sticker.vin

Contents render live at the address; this page states structure, not contents.

Every line posts with value · source · timestamp; where the OEM record is unavailable: “Reported, not yet verified.”

The record.

Every equipment claim traces to the factory order, or it doesn’t.

An ad, an auction sheet, and an appraisal can carry three different equipment lists for one car, each a retelling, none a citation. The build record is the factory’s order: what the OEM archive holds for one serial number, section by section, with plant and build date posted. “Sport package” either appears in the order or it doesn’t.

specs.vin states the vehicle as designed; this door states one car as ordered. Where the car and the record differ (an option removed, one added later) the delta is a fact worth having, and it belongs to the history at vhr.vin.

A claim that traces to the record is verified. A claim that doesn’t is the seller’s, and the delta is stated, not argued.

A build code is an ID.

The OEM’s codes are one provider’s names for the car.

A trim code, a color code, an option code: each is the OEM’s ID for a fact every other provider names differently. On the neutral Vindex ladder at vindex.vin, each code sits as a sameAs edge with a posted confidence, never a join key.

The identity manifestvindex.vin/{VIN}
1// 200 · the build’s codes as edges on one ladder, 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": <the OEM>, "id": <trim / color / option code>,
12 "confidence": <posted, 0–1>, "verified": <RFC 3339> }
13 ]
14}
Evidence
  • The build record’s codes resolve to every other provider’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, before purchase.

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

One record, two faces.

This door is the data. The print is one door away.

The data

build.vin

The as-built record as data: options, packages, and color codes as ordered, plant and build date stated; read, traced, and carried into the appraisal, the ad, or the negotiation. Reading the build is $0, every VIN, no account.

The same record renders as JSON for an agent: what it reads is what you read.

The document

sticker.vin

The window sticker: this record rendered as the document the car shipped with, options named and line-priced. The document tiers post their fees at sticker.vin beside the numbers the incumbents post; a number is posted or it is absent.

One row.

This dataset is one row in the Data catalog.

The what

data.vin

Every dataset behind this page is cataloged at the pillar door: coverage, license, posted price, and the x402 per-VIN bundle. This door owns one job: the as-built record, read free. The catalog sells the layer; this page never re-quotes it.

The how

apis.vin

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

Posted at this door.

A number is posted or it is absent.

Every line of the record posts with value · source · timestamp.

  • Read the buildEvery VIN · every visit · no account$0
  • The printed, line-priced documentIts fee posts at sticker.vinPosted there
  • The history after day zeroIts fee posts at vhr.vinPosted there

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 representationsbuild.vin
1curl https://build.vin/ -H 'accept: text/markdown'
2 # the markdown twin of this page
3curl https://build.vin/{VIN} -H 'accept: application/json'
4 # the record as typed evidence objects
5curl https://build.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 call
  • 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.
  • The gateNo gate on this door's two routes: keyless reads, no account. Gated actions elsewhere return a typed OFFER or a NEEDS_HUMAN handoff, never a dead end.