videos.vin
Become a Partner

the shelf / wiv-industry

What is Vin? The automotive industry’s record layer

What the film shows

Where does the record of a vehicle actually live? This film answers the industry-side question in seventy seconds: seventeen characters, one check digit, verified in place — and a record layer built on that spine.

Four pillars — data, services, commerce, AI — read as sets of addresses: the record, the work, the transaction, the agents. The full map is public. Type data and the record layer opens: the catalog, the as-built record, the crosswalk — each fact at its own address, with its source. On the wire, a fact is four fields: value, source, timestamp, verification. Every provider’s identifiers, mapped across one spine.

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.