the as-built record · the data layer
Build.vin
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.
A VIN is 17 characters and never uses I, O, or Q.
- build.vinThe as-built record — options, packages, colors, plant, build date. Free.
- sticker.vinThis record, printed — the window sticker as shipped
- specs.vinThe factory specifications — the vehicle as designed
- values.vinWhat this build is worth — five numbers, each with its basis
- vhr.vinWhat followed day zero — owners, titles, odometers; fee posted there
the build record at build.vin/{VIN}: $0 · every VIN · no account
01 · the record
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.
7MMVABDM3RN163785
2024 Mazda CX-50
- 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.”
02 · the seam
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.
03 · the codes
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 YMMTS spine at vindex.vin, each code sits as a sameAs edge with a posted confidence — never a join key.
A mapping posts only once verified, with its timestamp. Confidence is a number the reader reads, not an adjective this page uses.
- 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
// 200 · the build's codes as edges on one spine, evidence-stated { "type": "vindex.identity", "vin": "7MMVABDM3RN163785", "spine": { "year": 2024, "make": "Mazda", "model": "CX-50", "trim": <resolved, or candidates with scores>, "style": <resolved, or candidates with scores> }, "edges": [ { "provider": <the OEM>, "id": <trim / color / option code>, "confidence": <posted, 0–1>, "verified": <RFC 3339> } ] }
04 · the catalog row
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
- read the build$0 · every VIN · every visit · no account
- the printed, line-priced documentits fee posts at sticker.vin
- the history after day zeroits fee posts at vhr.vin
A number is posted or it is absent. Every line of the record posts with value · source · timestamp.
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
- B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
curl https://build.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://build.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://build.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one estate MCP server — 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.
No gate on this door's two routes — keyless reads, no account. Gated actions elsewhere on the estate return a typed OFFER (posted price · hard ceiling) or a NEEDS_HUMAN handoff, never a dead end.