2023 Tesla Model Y — what the estate has written
decoded from VIN · sample record · 2026-07-17 10:04 · check digit valid · both parties see this exact record
vehicle2023 Tesla Model Y Long Range AWD · verified
This record, posted across the family
the written record — pieces that touch this vin's questions
The Reading Plan — open, scan, follow.
- Open — blogs.vin, the whole corpus on one page.
- Scan — newest first, grouped by pillar, each piece dated.
- Follow — the piece at its own door's /blog address; the door's record instrument is one paste away.
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
- B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
curl https://blogs.vin/7SAYGDEE9PF947496 -H 'accept: application/json' → the record as typed evidence objects curl https://blogs.vin/7SAYGDEE9PF947496 -H 'accept: text/markdown' → the record's markdown twin curl https://blogs.vin/7SAYGDEE9PF947496 → this page
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.
Every door, this record
the pillars
- data.vinThe record layer's own door — every dataset behind the estate's pages, cataloged.
- services.vinCar services ordered by the VIN — the catalog the Services pieces write about.
- commerce.vinThe whole deal as one order — the settlement layer the Commerce pieces write about.
the family
- vin.companyEvery door, one record: vin.company/7SAYGDEE9PF947496