posted 2026-07-26 · cloud.motors.vin/blog/what-is-a-virtual-dealership-api-buys-real-cars
What is a virtual dealership — how does an API buy and sell real cars?
A virtual dealership is a licensed dealer that transacts through software instead of a lot; the API signs the deal while Vin handles title, payoff, taxes, registration, and transport.
A virtual dealership is a licensed car dealer that transacts through software instead of through a lot — the same license and the same legal obligations a rooftop carries, with an API where the showroom and inventory would be. Cloud Motors is one: a real, licensed dealership held by Vin that signs deals through an interface rather than across a desk. The API does not simulate a dealership or route you to one; it is the dealer of record on the deal. When it signs, Vin handles the licensed steps behind it — titles, payoffs, taxes, registration, and transport — while the counterparty on the other side of the call provides only funds and/or credit. That is how software buys and sells real cars: the license is real, the seat is real, and the API is the way the licensed seat is reached.
The instinct is to hear "virtual dealership" as a metaphor — a website that helps you find a car, with a real dealer somewhere behind the curtain. It is the opposite. The website part, the finding-a-car part, lives at the doors. The virtual dealership is the licensed counterparty itself, stripped of everything that is not the license. No lot, because it stocks nothing. No floor plan, because it floors nothing. No salesperson, because it is not trying to move a unit. What is left is the one thing a lawful car transaction structurally requires and a private party cannot conjure: a licensed dealer to sign as dealer of record. An API is just the honest shape for that, once you remove the lot.
What the API actually does when a car changes hands
A car transaction is a sequence of licensed acts, and each is an API operation rather than a paper step:
- Title — signed and perfected by the dealer of record, keyed to the VIN.
- Payoff — the seller's lien retired against the sale, so the buyer's funds clear the loan first.
- Taxes and fees — the out-the-door total computed to the buyer's state, itemized.
- Registration — filed in the buyer's state, alongside the title, not as a later errand.
- Transport — quoted from a VIN and two zip codes, tracked to the door.
None of these is invented by the software. Each is a licensed act the dealership is entitled to perform, exposed as an operation the deal moves through in order. The counterparty calls the API — or an agent calls it on their behalf — and brings the two inputs the license cannot supply: funds and/or credit. Everything between those inputs and the delivered car is the dealership's work, run through software. The car is real, the title is real, the plates are real; only the storefront is gone.
Why the money never moves before the record does
The reason an API can be trusted with a real car is that no figure on it is invented. Every money line on an order is a slot — a payoff, a tax total, a transport quote — that reads as unfilled until its source supplies the number. The software does not estimate the payoff and reconcile later; it holds the slot open until the lienholder's actual figure lands, then posts it. This is what lets the whole deal be read before anything signs: you are not looking at a quote the machine made up, you are looking at the real lines as their sources fill them. Reading the rail and its deal shapes costs nothing and needs no account.
That fill-from-source discipline is also what makes the deal safe to run at machine speed. Because each line traces to its own source and its own address, an agent transacting on a Mandate can read exactly what a person reads and settle programmatically, with the fee disclosed, without anything being hidden inside another line. The API signs what the page attests; the page attests only what the record can fill.
One rail, three deal shapes, one order
The virtual dealership is a single licensed seat that serves more than one kind of deal. The kernel's first deal type runs on it: Wholesale Dropship, at dropship.vin — a unit bought at the wholesale lane and delivered straight to a buyer's driveway, never stocked on a lot. Cloud Motors signs as dealer of record; Vin handles title, payoff, taxes, registration, and transport; the buyer brings funds and/or credit. No lot, no floor, no reconditioning-to-frontline markup — the unit stocks nowhere between the lane and the driveway. The same seat also sits between two private parties, or dispositions a consumer's car into the lane; the ends differ, the licensed middle does not.
Whatever the shape, the deal the API signs settles as one order at commerce.vin, each line at its own member address — the rail never competes with the doors it makes lawful. And there is one honest limit on the software: an API can sign only where the license underneath it is in place. Dealer licensing is per title-taking state (entity, bond, place of business), so the virtual dealership signs as dealer of record in a state once that state's licensing clears; until then, in that state, it quotes and attests every line for free but does not yet sign. The reading is national and free today; the signature follows the license, state by state. If you already found the specific car you want to buy end to end, the consumer door that runs on this seat is buy.vin.
The record, at its other addresses
- commerce.vinThe pillar door: the whole deal settles as one order, each line at its member address
- buy.vinBuy: the consumer door — the rail holds the dealer seat where the deal needs one
- offers.vinSell: a real cash offer for any VIN, payoff handled
- dropship.vinWholesale Dropship: bought at the lane, delivered to the buyer, never stocked
- transport.vinTransport: a VIN and two zips, tracked to the door
- dealers.vinThe dealers' entrance to the VIN rails: appraise, pull records, wholesale, move