The shelfwiv-dealers
What is Vin? How your store becomes agent-answerable.
Seventy seconds from the counter’s side: one number per unit, four rails your inventory rides; or rides none.
What the film shows.
Every fact on screen is real.
You sell cars, here’s the short version of Vin: one number per unit, a number that checks itself, and four rails your inventory rides, data, services, commerce, AI, or rides none.
Seventy seconds from the counter’s side: the map of every address on one page, searched the way an agent would search it. Type sell and the tree narrows to the counter: the listing, the offer, the paper. Post the number, take the offer; the dealer of record runs in the cloud. The close is two stores side by side: one says call for today’s price, one posts the record. The agent reads one of them.
The addresses the film names.
Each one answers at its own address.
Data room.
The source copy posts on request.
- Source copyThe mp4 finals, held privately by Vin; posted on request.
- The film aboveThe public copy, on Vin’s channel: a privacy-enhanced embed (youtube-nocookie.com), no cookies until play.
For the agent you send.
The agent reads the same record you do.
Same two routes, three representations: the numbers never differ between them.
- Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the call
- Machine surfaces/llms.txt/icp.json/.well-known/agents.json
- One MCP serverapis.vin/mcp serves the whole platform: every door’s tools in one server, each result carrying its door’s URL.
- AttributionX-Client-Type: html | md | json | mcp names which reader arrived; it never changes the record.
- The gateNo gate on this door's two routes: keyless reads, no account. Gated actions elsewhere return a typed OFFER or a NEEDS_HUMAN handoff, never a dead end.
