the appearance face · FIX lane · Services
A professional detail, ordered by the number.
Quote. Book. Shown.
The decode supplies size, class, and trim — the facts the counter would have asked — so every package posts its price before the car moves. The order tracks to done, and the completion posts to the record, photos beside it. The quote posts on request. No account.
Hand this record to your agent: it walks the quote and the order through the services counter, and you appear only where you’re load-bearing — authorize the work, hand over the keys.
A VIN is 17 characters and never uses I, O, or Q.
one package, as it posts
- the package— tiered from size, class, and trim — never a glance at the curb
- the posted price— vendor cost, our margin, and the total, each a posted line
- the status— webhook posts distance-to-done on the order record
- the completion— order id, package, timestamp, photos — posted to the record
prices from decode · size class · trim — before the car moves
Packages, prices, and statuses render live at the address. This page states structure, not prices.
The counter menu is not a posted price.
“Call for pricing” is a ritual standing where a number should be. Here is what posts instead.
- “Call for pricing”?every package posts its price from the decode — before the car moves
- “Starting at…”?the posted price: vendor cost, our margin, and total as separate lines
- “Once we see it…”?size, class, and trim post from the VIN — no counter revision, no “we quoted a sedan”
- “While it’s in the bay…”?no line appears at settlement that wasn’t on the quote — the price posted before the keys did
Every line posts with the same evidence grammar as every other line on the record: value, source, timestamp. The vendor sees this exact page.
The order, on the services chassis.
Quote → book → shown. The order transacts through the services.vin counter until this door’s own flow ships — one VIN, one order, one invoice.
01Quoteposts on request
Paste the VIN. The decode supplies size, class, and trim — the facts the counter would have asked — plus the one input the job needs: where the car is. Every package posts its price on request through the services.vin counter, vendor cost and our margin as separate posted lines.
the vendor cost · our margin · the total
02Bookopens when the gate clears
Pay the posted price; the order opens at the address. The bay is scheduled, the keys hand over, and the order posts its status — webhook by webhook — distance-to-done.
the appointment · the status · the package
Book the detailnot yet open · vendor agreements for the detail-and-appearance cluster before paid orders
Order actions render through the compliance gate: vendor agreements for the detail-and-appearance cluster run through the services.vin chassis; until they clear, nothing on this page takes a paid order. The quote posts on request today.
03Shownposts to the record
The completion posts to the record — order id, package, timestamp, photos. A detail that posted happened; one that didn’t post is a claim. The record is dated — work argued later argues from a timestamp.
the completion · the photos · the order, dated
Order id, timestamps, and amounts render live at the address. Structure, not prices.
Before and after are condition facts.
The photos post to the record with the same evidence grammar as every other line — value, source, timestamp. Before documents the panel as the car arrived; after documents it as the work left it. Neither is an ad.
A seller’s listing carries a detail buyers can read, not one they must take on faith. A dealer’s recon line carries a completion the desk can audit. The gloss is the counter’s register; the record posts condition.
Posted condition, dated. Never marketing gloss.
serves this doordetailing → detail.vin
Inside recon, the same rail.
A detail order inside a dealer’s recon work order rides the same rail as one ordered at this door — same VIN, same counter, same record. What the inspection finds, recon fixes; the detail is the cosmetic close of the same unit — the condition face answers at inspection.vin.
A store’s saved specification — inspect, recondition, detail — bulk-orders per VIN list at net terms, vendor cost and margin posted per line, per unit.
One unit, one record. The detail is its cosmetic close.
Who orders it.
One posted rail, three registers — the same packages, the same posted lines.
The seller
the listing carries the detail
Preparing the car for the listing, the seller orders the package and the completion posts to the record the listing reads — a detail buyers can verify, dated before the first showing.
listings.vinthe listing reads the posted record
offers.vinthe offer reads the same record
the completion posts · the listing reads it
The dealer
recon detail, per VIN, at net terms
The used-car manager orders detail inside recon — one saved specification, bulk-ordered per VIN list, vendor cost and margin posted per line, per unit. The desk audits completions, not promises.
inspection.vinthe finding drives the work order
dealers.vina store reads the same rail
posted per line, per unit
The owner
keeping the car right
The same package prices from the decode for a car that isn’t going anywhere. The completion posts to a record the next owner reads — care that is a fact, not a recollection.
maintenance.vinthe keep lane on the same record
values.vinfive values, posted free beside it
the completion posts · the record keeps it
The detail is one face of the record.
If an agent orders the detail for you, it reads this same record: the posted quote · the order status · the completion with its photos is the receipt that survives being shown to you — tools at apis.vin/mcp.
For the agent you send
The agent reads the same record you do. Same two routes, three representations — the numbers never differ between them.
motions: B2A · B2A2C
- B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
- B2A2C — an agent acting for a consumer — everything it does survives being shown to them afterward
curl https://detail.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://detail.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://detail.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one estate MCP server — apis.vin/mcp (every door a lens; tool results carry the door URL).
Attribution: X-Client-Type: html | md | json | mcp — read for agent-led demand attribution; it never changes the record.