pitch.all.vin
One VIN field, every door.
Every car, both sides. The family front door: paste a 17-character VIN and every door — history, value, sticker, recalls, buy, sell, finance, insure, ship — opens on the same record.
↓ scroll · arrow keys
The car trade runs on an information-asymmetry ritual — the desk — and the desk's first move happens before anyone negotiates: the facts about one car are scattered across a different counter for every question. History at one address, value at another, recalls at a government form, the payoff a phone call, the sticker gone with the first owner. Whoever consolidates first — and it is never the consumer — starts the deal knowing more.
The person this door serves arrived with a VIN and a decision: check it, buy it, sell it, finance it, insure it, move it. They don't know which door they need. They know the number — and the number is enough, because a VIN is seventeen characters whose ninth exists only to certify the other sixteen.
Paste the VIN once. The hub decodes it and fans out to every member door as
{brand}.vin/{VIN} — each link carrying a posted context chip from the
record, never a pitch. The record chooses the door: an open-recall count
routes differently than a lien reported and not yet verified.
A labeled specimen of the fan-out grammar — illustrative product mechanics, not live data:
vhr.vin/{VIN} — "History: 14 records · last posted 2026-06-30"
values.vin/{VIN} — "Value: $18,400 retail · $16,900 trade · posted"
recalls.vin/{VIN} — "2 open recalls · posted" (attention state when > 0)
buy.vin/{VIN} — "Listed · 7-step checklist · you're 7 steps from done"
offers.vin/{VIN} — "Sell: instant offers against posted value"
transport.vin/{VIN} — "Ship: quote from this VIN and two zips"
The anti-directory rule is architecture, not editorial policy: chips are live data or absent. A door with nothing posted shows "No record posted" — never marketing copy. No door is recommended; the record's state does the routing.
b2a.vin cluster · apis.vin
the motions: who buys, who approves, who gets the receipt
buy.vin · offers.vin · fi.vin · insure.vin · taxes.vin · commerce.vin (pillar)
member fees post at member doors
transport.vin · services.vin (pillar)
quote → order → invoice, one VIN
vhr.vin · values.vin · recalls.vin · sticker.vin · data.vin (pillar — held mark)
free doors first; paid documents post their fee
The family's constitution is a three-way split, and the hub's own row is mostly prohibitions. all.vin owns the company claim, the canonical record address, and the fan-out to everything — and never a member's job, a layer's depth, or a transaction. The pillar doors own each layer's claim. The member brands own their one job, their fees, their canonical faces. Traffic flows down; value flows through the members. The pillar catalogs shrink to links as members ship — that is the design.
The filing is governance of record, not deck copy: the registry's founder ruling attests family=vin, primarySurface=all.vin, and always-renew across the pillar rows — the front door is the one address the estate is built never to lose.
One held mark, worn openly: data.vin — the record layer's catalog — is HELD under an unsigned agreement, and the registry's ruling is that no surface hyperlinks it until r4 signs. This deck honors the ruling in its own bytes: data.vin appears here as a plain mark and this record hyperlinks nothing to it. The live family page at vin.company does not yet honor it — it hyperlinks data.vin today — a violation worn here as candour, with reconciliation queued, not papered over. The family map shows held names as marks, never as doors.
Liveness is a claim here, never an ambient fact — one claim per door, each with its own evidence URL, each true on the day this record was filed.
The apex resolves today: all.vin answers with a 301 to the family front door at vin.company. The address works; where it serves from is stated plainly in the pending claim below, not papered over.
The family front-door page itself serves: the VIN field with live decode, the full Data → Services → Commerce → AI spine, and the fan-out of member doors with per-layer addresses — the page this deck describes, loadable by a stranger.
The record address resolves: all.vin followed by a VIN 301s to the family record lens for that VIN, which serves. The hub's canonical-address claim is a working URL, not a diagram.
values.vin serves: five market values for any VIN — auction, wholesale, trade-in, private party, retail — posted with source and timestamp, free, no account.
recalls.vin serves: every open NHTSA campaign on a VIN — campaign number, component, remedy, repair status — free, at one address.
The decode underneath is the sibling rails: auto.dev's APIs, documentation, and rate card are public on its own domain. The hub buys its first call from the family's own data plane.
The honest gap between filing and DNS: the registry files all.vin as the family's primarySurface, and today the apex serves that surface by redirect rather than at its own address. This claim flips when the hub answers at all.vin directly — until then, the 301 is stated, not hidden.
The motion is B2C, search-led: people at a car moment search the question the scatter forces on them — what's this VIN worth, is this VIN recalled, what's this car's history — and each free door answers its question whole, no account, no counterparty. Every answer is one click from the record, and the record is one click from the deal at a member door. The hub is the authority spine those doors link back to; that loop is the ratified role, and it is the whole marketing budget.
One ICP, chosen explicitly: the consumer holding a VIN. The other actors have their own entrances and are cross-routed, never courted here — the dealer's door and the developer's gateway each state their own case at their own address.
The dealer entrance serves at dealers.vin — appraise, pull records, move cars — so the hub can stay one-hero without abandoning the other side of the deal it posts records for.
The front door resolves today: paste a 17-character VIN after all.vin/
and the record answers.
If this was forwarded to you: all.vin is the front door of the VIN family — one field where any 17-character VIN fans out to every door of a car deal, each fact posted with source and timestamp, each door at its own address, the hub's own fee $0 and posted. Every liveness statement above carries its own state and evidence URL, including the two ambers the door wears openly: the held data.vin mark this record shows without a hyperlink until r4 signs (a ruling the live family page has yet to be brought under), and the apex serving the family page by redirect until it answers at its own address — each pending until it's true.