pitch.services.vin
Every service a car needs, ordered by its number.
The operational pillar of the VIN estate: inspection, transport, title and registration, detail, repair, storage, tow — one VIN, one quote, one paid order, one invoice.
↓ scroll · arrow keys
You can find the car, check its history, and settle its price from a couch. Then the deal turns physical — an inspection before the deposit, title and registration after the close, a truck to move it — and every one of those jobs falls back a century: five phone calls per job, a price that firms up only at the counter, a different vendor for every step, and no record of any of it afterward. The desk's local franchise is the callback chain, and it taxes every job a car ever needs, in a deal or out of one.
The person this door serves arrived with a VIN and a checklist: the remote buyer whose deal has physical steps left and no counter to order them from. The same scatter bites the owner between deals — the smog check, the detail, the month of storage, each booked by phone tree — but the door is keyed to the moment the work blocks a deal, because that is when the callback chain costs the most.
The vin family's constitution is a three-way split, and this door exists because one job belongs to nobody else. all.vin — the one aggregate — routes every VIN to every door and transacts nothing. The member brands own their one job outright: transport.vin is live, so this door never quotes transport — the MOVE row is a link with posted context, and the move is always the member's order. services.vin owns what remains: the cross-service order — inspection and title and delivery on one car as one invoice — and the sale of every service whose member door has not shipped yet.
Graduation is a pointer swap. A held service — mobile inspection, title work, detailing — transacts at this address today: same order type, same canonical name, same ledger stream. The day its member door goes live, the catalog row converts to a lattice link and the member owns its moment — a data change, never a layout change, with no canonical migrating and no redirect debt. The pillar's catalog shrinks to links as the family grows. That is the design, not a failure mode.
Every lane sells through the same four hops, on the proven commerce-services chassis — the legacy Driv.ly services pattern absorbed into auto.dev and reserved for exactly this door. The quote posts from the VIN, free. The paid order opens at the posted price with vendor cost and our margin as separate lines. Webhooks post distance-to-done. An order attached to an open deal settles under the parent invoice's one total.
the order chassis
The quote side of the chassis is live on the counter today: the landing states it in its own words — "The quote is live today — every job prices from the VIN, free, no account."
The order side is gated, and the counter says so on the page: order actions render through the compliance gate, and until vendor agreements per cluster and the per-state title/registration gate clear, nothing on the page takes a paid order. The claim that matters — a real paid order, its vendor cost and margin posted as separate lines — posts here when it has happened, with the order record in evidence.
The catalog sells in five lanes — MOVE · FIX · PAPER · KEEP · POWER — move the car, work on the car, paper the car, keep the car, charge the car. A lane is a shelf, not an address: no lane ever mints a door, and every rendered row is a transactable offer or a lattice link with posted context — never a bare name list. If a section would still work as a list of domains, it fails; that is the family's anti-directory rule, applied to this door's own catalog.
The MOVE lane shows the whole constitution in one row: transport.vin is the lane's flagship and the pillar's reference implementation — the quote-to-order chassis proved out on it first — so its row is a link that sends the order to the member, never a re-quote. The FIX lane runs inspection and recon as one unit: the finding drives the work order, and a completed inspection posts its facts to the record — new posted evidence the family serves back out. The PAPER lane is where the compliance gate bites hardest, and the page states it as a fact: where a state's gate has not cleared, the row reads "not yet offered in that state."
The live member is real: transport.vin serves — ship any car from a VIN and two zips, quote to delivered — the member this pillar links to and never re-quotes.
The model is the transport.vin economics generalized to the catalog: dispatch margin per paid service order, with vendor cost and our margin posted as separate lines on every order — the estate's posted-fee grammar applied to physical work. Quotes are free. No subscriptions: a price is posted or the service is not offered. This record asserts no figures; every number posts on an order page at order time, in evidence grammar.
Three compounding layers, stated as structure:
The motion is B2C on two intakes. Search-led: the catalog intent — "order car services by VIN," "pre-purchase inspection and shipping, one order" — is disjoint by construction from every member's single-job intent and from the hub's platform intent, so the lattice never competes with itself. And spine-led: the family's own deals name their physical steps — the purchase checklist's inspection step, the sale's pickup step, the history report's "the record says accident — order the inspection" footer — and each step lands on this counter already holding its VIN.
One ICP, chosen explicitly: the remote buyer mid-deal. Owners between deals walk through the same catalog intent. The other actors are named and cross-routed, never courted here: transport shoppers belong at transport.vin and the page sends them there; dealers buy bundles at their own entrance; agent callers order over the machine surface. A door is one ICP and one motion — the pillar holds the layer, not every buyer in it.
Liveness is a claim here, never an ambient fact — one claim per surface, each with its own evidence URL, each true on the day this record was filed.
The counter serves: the Services-layer landing at services.vin — the five-lane catalog in posted grammar, the free VIN quote console, and the order chassis stated hop by hop, with the compliance gate worn on the page rather than hidden.
The service face serves: services.vin followed by a VIN renders the record's service lens — decode identity, the record posted across the family, the fan-out to the doors that answer it — labeled as a sample record and noindexed, exactly as the pillar-lens rule requires until it carries posted service-order facts of its own.
The same address answers machines: request it with accept: application/json and the lens returns the record as typed evidence objects — value, source, timestamp, verification state — one address, two representations, numbers that never differ between them.
The pillar's live member serves: transport.vin, the MOVE lane's flagship — the proof that the quote-to-order chassis works at a member door, and the standing demonstration of the row-to-link rule.
The family front door serves: the VIN field with live decode and the full Data → Services → Commerce → AI spine — the layer this door anchors, rendered on the page a stranger can load.
The rails underneath serve: auto.dev's APIs, documentation, and rate card are public on its own domain. The decode that prices every quote is the family's own data plane, bought at its public card.
The honest gap, stated twice because it is the one that matters: quotes are live and paid orders are not. This door's first commercial fact — a settled service order with its itemized lines — posts here with the order record in evidence, and is never implied before it exists.
The counter is live at services.vin — paste a VIN and every lane
quotes from it, free, no account.
If this was forwarded to you: services.vin is the operational pillar of the VIN estate — the one counter where every physical job a car needs is quoted free from its VIN, ordered at a posted price with vendor cost and margin as separate lines, tracked by webhook, and settled on one invoice; where a live member door exists, this door links to it and never competes with it. Every liveness statement above carries its own state and evidence URL, including the amber the door wears openly: quotes are live today, and the paid-order claim stays pending until the compliance gate clears and a real order record exists to cite.