pitch.commerce.vin
The whole deal. One order.
The car, the taxes, the loan, the insurance, and the delivery settle as one order — every line posted, every line at its own address. Built on the VIN by Vin. This page's own fee: $0.
↓ scroll · arrow keys
Buying a car "entirely online" is still five transactions wearing one intent: the purchase in one tab, the loan at the bank's, insurance behind a 40-question form, taxes discovered at the end, shipping a phone call — and every counter re-asks the same facts about the same car. The desk's four-hour close became five tabs, and no page anywhere shows the whole deal. Selling is worse: the offer, the payoff, and the pickup are three different companies who have never heard of each other.
The person this door serves holds the one intent no member door names: the whole thing, as one transaction. buy.vin owns buying, offers.vin owns selling, financing.vin owns the loan, insure.vin owns the binding, taxes.vin owns the out-the-door math — and this door owns the claim that those settle as one order on one spine. It proves that claim with a rendered order, not a slogan.
Paste a VIN. The order assembles: five lines, each a full product at its own address, each wearing its state on the order — and exact figures compute at the address, by state, before you commit. One correlation spine underneath: a prequal, a bound policy, and a booked delivery attach to the same order without re-entering a fact. Selling runs the same rail in reverse — a real cash offer from the VIN, payoff handled, pickup booked on the same order record.
The live demo order, re-set as a specimen — {VIN} stands in for the
demo VIN the page renders in full; real structure, never invented
figures, every line carrying its state:
commerce.vin/{VIN} 2024 Mazda CX-50 · decoded
01 Vehicle buy.vin/{VIN} the close, end to end online posts live
02 Taxes, title, DMV fees taxes.vin/{VIN} out-the-door by state, itemized posts live
03 Financing financing.vin/{VIN} prequal attaches — no inquiry until you apply posts live
04 Insurance insure.vin/{VIN} quoted from the decoded spec bound at close
05 Delivery transport.vin/{VIN} quoted from a VIN and two zips posts live
Out the door one total, one order posts live
commerce.vin fee: $0 · every line settles at its own address · none settles here
The door serves today: the live page renders the one-order hero, the assembled demo order for a decoded 2024 Mazda CX-50 — every line at its member address, wearing its state — the consumer and dealer registers, and the door's own fee posted at $0.
The order face resolves: commerce.vin followed by a VIN serves the order assembly for that record — a working URL a stranger can load, not a diagram.
buy.vin · offers.vin · financing.vin · fi.vin · insure.vin · taxes.vin
member fees post at member doors; figures compute at the address
dealers.vin (flagship) · desking.vin · auction.vin · wholesale.vin · tradein.vin · floorplan.vin · appraisal.vin
two counters, one ledger — the registers touch at the trade-in
cloud.motors.vin · dropship.vin
title, payoff, taxes, registration handled; the unit never stocks anywhere
payments.vin · escrow.vin
the money moves at the member; none of it moves here
The family's constitution is a three-way split, and this door's row is
mostly prohibitions. all.vin owns the company claim and the fan-out to
everything. The member brands own their one job, their transactions,
their fees, their canonical faces. commerce.vin owns exactly one thing
— the layer claim, one-order settlement — and is structurally forbidden
the rest: no member's job intent, no transaction, no take rate, no
canonical /{VIN}. Traffic flows down, hub → pillar → member; value flows
through the members only. Held names on the layer map render as plain
marks — never links, never counted — until each ships under the minting
law.
The dealer-of-record rail, stated at its true state: designed to be owned — Cloud Motors, the licensed virtual dealership signing as dealer of record for deals that require one — and not yet in production. Until cutover, the steps the law reserves for licensed people are done by licensed partners, with the boundary stated on every transaction. Same gate as the company record; the two files cannot drift.
Liveness is a claim here, never an ambient fact — one claim per address, each with its own evidence URL, each true on the day this record was filed. Serving is a liveness fact, not a settlement claim.
The vehicle line's address serves: buy.vin — buy any car by its VIN, end to end online.
The taxes line's address serves: taxes.vin — the out-the-door price; taxes, title, DMV fees by state.
The financing line's address serves: financing.vin — financing from a VIN; soft-pull prequal to funded loan.
The insurance line's address serves: insure.vin — insurance that starts from the car, not a 40-question form.
The delivery line's address serves: transport.vin — quoted from a VIN and two zips. The one licensed cross-layer line: the order shows the whole deal, and the deal ships at a services-layer member.
The reverse rail serves: offers.vin — sell your car by its VIN; real cash offers, payoff handled.
The layer's own claim, at its honest state: the addresses serve and the order face renders, and no stranger's whole deal — vehicle, taxes, financing, insurance, delivery as one settled order — is posted yet. The claim that matters flips when it has happened, with the settled order in evidence. One-order settlement is never implied before it exists.
The motion is B2C, search-led: the door indexes on the layer-category
intent — automotive commerce platform, whole-deal one-order transaction,
"buy a car entirely online in one transaction" — which is disjoint by
construction: the hub's grammar claims the company, each member claims its
job, this door claims the layer. Zero overlap with its own family. The
order face at /{VIN} stays out of the index on purpose; the landing
carries the intent, the members close the deals, and the door gets out of
the way.
One ICP, chosen explicitly: the consumer holding whole-deal intent. The other readers this layer attracts have their own entrances and are cross-routed, never courted here.
The dealer entrance serves at dealers.vin — the dealer register's flagship, the store-side counterparty face of the same ledger — so this door stays one-hero without abandoning the other counter.
The developer and agent entrance, at its honest state: the estate files apis.vin as its one MCP server and typed offers, and today that address serves the sibling data plane's gateway — auto.dev's discover catalog, signup and docs pointing at auto.dev — while apis.vin/mcp does not serve. When the entrance ships, an agent closing a deal for a person reads this page's order, unchanged; the pillar describes the capability, and apis.vin transacts the API relationship.
One held mark, worn openly: the layer line this door sits in — Data → Services → Commerce → AI — has its data pillar, data.vin, HELD under an unsigned agreement. The registry ruling is plain mark only — no hyperlink — until r4 signs, and this record honors it in its own bytes: this deck shows data.vin as a plain mark and hyperlinks nothing. The estate does not yet honor it everywhere — this door's own live apex still hyperlinks data.vin in its estate-layers nav (curl-verified 2026-07-30), and the de-link is queued as a root-surface fix. Candour over completeness.
The front door is commerce.vin — it serves today, and the order
assembles.
The history door serves at vhr.vin, with a free rung on every VIN — decode and open-recall check free; the full report is $19.99.
The value door serves at values.vin — five values (retail, private party, trade-in, wholesale, auction) for any VIN. Free, no account.
If this was forwarded to you: commerce.vin is the transaction layer of the VIN platform — the door where a whole car deal (vehicle, taxes, financing, insurance, delivery) settles as one order, every line posted at its own member address, the door's own fee $0 and posted. Every liveness statement above carries its own state and evidence URL, and the deck wears its four ambers openly: no whole deal has settled as one order yet, the dealer-of-record rail awaits its production cutover, the developer-and-agent entrance at apis.vin awaits its own MCP surface, and the family's data pillar stays an unlinked mark until its agreement signs. Paste a VIN at commerce.vin — or forward this to the person project-managing five tabs into one car.