Dealers

The market has two sides over one Deal ledger — the demand side (the consumer) and the supply side (the dealer). This section is the supply side: the store, online or on a lot. 45 catalog rows are supply-initiated; another 62 run on the facilitator rail beneath both counters.

Two counters, one ledger. The same VIN, the same numbers, read from either side.

Agent-answerable is the new certified

Buyers' agents now arrive mid-checklist and read what a store has posted — or route past it. A store makes its inventory legible to those agents:

• inventory.post — put a vehicle on the record.
• inventory.read — make it answer an agent's questions, in the same evidence shapes the record uses.
• listing.distribute — list it across venues.

What is not answerable is invisible to the agent doing the shopping. Posting is the floor; answerable is the bar.

The service drive

Roughly half a franchise store's gross profit lives behind the service counter. The shop-ops rows run repair orders, parts, warranty, and recon on the same quote → order chassis as every other Service:

• ro.repairOrder — open and grow a repair order as issues are found.
• part.matrixPrice — price parts.
• warranty.claim · recon.order — claims and reconditioning.

The deal, papered

The commerce rows fold onto one Deal ledger — a deal is a composition of standalone acts, never a monolith:

• deal.desk — structure the numbers (a desk-manager credentialed step).
• otd.reconcile — itemize the out-the-door price.
• fni.select — present and select protection.
• insurance.bind — bind coverage (a licensed producer step).

Buy the whole walk as the buy workflow, or call any leaf on its own address.

Wholesale and the money supply side

The supply side of the money — wholesale, floorplan, appraisal, salvage — is first-class, not an afterthought:

• bid.place · appraisal.quote
• floorplan.status · salvage.channel
• lead.capture · lead.adfExport

The integration layer

A store's existing systems — its DMS, its auction standing, its rails — connect through the integration layer, faced for the dealer at integrates.vin and, for the consumer, at connects.vin. Both are branded human faces over one machine rail (apis.vin/connections/*): link → credential ceremony → connected account → sync → account-verified evidence.

This is the one place a provider name lives. The abstract product face — the record, the catalog, every evidence object — speaks only the estate's own capability vocabulary; who fulfills a capability is invisible to the caller. The two layers are walled, and the wall is a tested invariant.

Next

• Doors — every .vin door and its held shelf.
• The catalog — the Commerce and Services rows in full.
• The record — what both counters read.