What tools does a dealer get from the VIN platform — appraisal, records, disposition, and transport by VIN?

A dealer working the VIN platform gets four rails, each keyed to the unit and each reached from the same account: appraise a unit against real transactions at values.vin, pull its full record at vhr.vin, take wholesale disposition with the payoff handled at offers.vin, and dispatch transport from nothing more than a VIN and two zips. There is no separate login per tool and no per-seat portal to learn — one account at auth.vin opens every address for the store, and every rail resolves against the same VIN, so the number the appraiser reads is the number the desk prices from and the record the buyer reads.

That is the whole shape of it, but the shape is the point: these are not four products bolted together. They are four faces of one unit. A car on your lot has an address; at that address it decodes, it prices, it carries its history, and it can be moved. What follows is what each rail actually does, described exactly as the store connects it.

Appraise against real transactions, not an opinion

The appraisal rail lives at values.vin. Enter a VIN and it returns five value bands — retail, private party, trade, wholesale, and auction — with the comparable-transaction set behind each one. The distinction the rail is built on is that book is an opinion and the comps are a record: the number is not a single guru figure to accept or argue with, it is a band with the sales that produced it shown underneath. A used-car manager reads the band before quoting a trade, and the appraiser adjusts from that basis line by line against inspection facts rather than starting from a guess.

This matters for a store because the whole cost of the old way is argument. When the appraised number has its comps attached, the conversation with the customer stops being whose figure do we trust and becomes here is the record and here is the adjustment. The desk stops spending its margin proving it isn't the crooked store down the street.

Pull the full record, once, per VIN

The record rail is vhr.vin: history, recalls, window sticker, and value on one page per VIN, pulled once. Instead of assembling a unit's story from four vendors and four tabs, the store pulls the record at the VIN's address and it is there — the history behind the unit, the open recalls, the original build, and the current value bands in one place. Because the value on that record page is the same value the appraisal rail returns, there is no reconciling two numbers from two systems; it is one record with many faces.

The own-data faces — the decode, the resolved VIN, the value band — lead and cost nothing to read. The deepening steps that carry a licensed cost, such as the full third-party history overlay or the OEM build data, are priced on their own page like every other number, so the store sees the cost of accuracy before it commits to it rather than after.

Take disposition with the payoff handled

When a unit is a wholesale candidate rather than a retail one, disposition runs at offers.vin: the store takes a firm number to move the metal, and the loan payoff — if the unit still carries one — is pulled and settled inside the transaction rather than left as a separate chore. The decision of whether to retail or wholesale a given unit is its own analysis (the spread between the auction band and the retail band, read against the unit's aging in days), but once that decision is made, disposition is a rail, not a phone tree.

Dispatch transport from a VIN and two zips

The transport rail dispatches from a VIN and two zips — origin and destination — and tracks to the door. There is no separate freight portal, no re-keying the vehicle details a third time; the unit is already resolved, so dispatch inherits what the VIN already knows and the move is tracked back onto the record. This is the rail that turns a bought unit into a delivered one, whether it is coming off a lane or going to a buyer.

One entrance, one key

The reason these read as one entrance and not a bundle is the connection layer. The store connects once at auth.vin, and every address opens; to embed the rails into a DMS or a storefront, apis.vin exposes one key, one SDK, and one MCP server, with the reserved acts — the ones that require a credentialed hand — routed to those hands rather than left open. Inventory, records, values, and settlement flow through that single seam. A store's own developers wire it the same way an AI agent reads it: at the address, in typed data, against what the record states.

The honest limit is worth stating plainly. dealers.vin does not sell placement — there is no pay-to-rank feed, no sponsored inventory, no lead-resale. Each rail posts its own price on its own page. What the store gets is not visibility bought at auction; it is a unit that answers at its address, to a human at the desk or an agent presenting a Mandate, from the same record both sides read.

For the numbers themselves, start at values.vin to appraise a unit against its comps, or pull one full record at vhr.vin to see the whole story on one page. Both are faces of the same VIN, and the store prices from the record its buyer already reads.