videos.vin

the shelf / tell-your-agent

Tell your agent: one address makes it a car expert

What the film shows

Ask your AI assistant a car question and you get answer-shaped noise — fluent, sourceless, unverifiable. This film adds one string to the assistant’s connectors — apis.vin/mcp — and asks again. No code anywhere in the film. That’s the point.

The connector is keyless: three tools — search, fetch, exec — and the whole technical act takes about eight seconds. Then the same question walks the estate: tool calls on the wire as real MCP JSON, doors answering with evidence, every answer typed — OK, empty, blocked, offer. One connector, different askers: a consumer prices a car, a dealer runs the counter, an analyst decodes a fleet, a creator checks a shelf.

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.