videos.vin

the shelf / wiv-dealers

What is Vin? How your store becomes agent-answerable

What the film shows

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

Data room

  • source copymp4 finals, 2026-08-10 — held in the estate's data room; posted on request
  • the film abovethe public copy, on the estate's channel — privacy-enhanced embed, 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.

motions: B2A

curl https://videos.vin/ -H 'accept: text/markdown'        → the markdown twin of this page
curl https://videos.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://videos.vin/{VIN} -H 'accept: text/markdown'    → the record's markdown twin

Machine 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.

No gate on this door's two routes — keyless reads, no account. Gated actions elsewhere on the estate return a typed OFFER (posted price · hard ceiling) or a NEEDS_HUMAN handoff, never a dead end.