blogs.vin
Become a partner

blogs.vin/7SAYGDEE9PF947496

2023 Tesla Model Y.
What the platform has written.

Σ value × weight = 504 ·504 mod 11 = 9 · position 9 reads 9

Decoded from VINSample record2026-07-17 10:04Check digit validBoth parties see this exact record

Any VIN, one addressblogs.vin/{VIN}

Check digit: a North American convention, not applicable to this WMI

The build, decoded

  • BodySUVSample recordPosted 2026-07-17 10:04Verified
  • Drivetrain4WDSample recordPosted 2026-07-17 10:04Verified
  • Engine5.0L V8Sample recordPosted 2026-07-17 10:04Verified

What the seventeen characters certify

  • Check digitPosition 9 reads "9": the other sixteen compute "9"ISO 3779 · 49 CFR 565.15(c) check-digit mathVerified
  • Validation regimeNo mandate established, validated structurally, fail-open · Oceania 7 block, historically New Zealand, with attested US assignments (7SA/7FC/7PD/7JR)ISO 3780 allocation history with observed drift (vindex wmi-structure, vin-84j.26): the region map never hard-fails a VINReported, not yet verified
  • Manufacturer idWMI 7SA: positions 1–3ISO 3779 VIN structureVerified
  • Model-year codePosition 10 reads "P": the 2001–2030 code table reads 2023ISO 3779 model-year tableVerified
  • PatternSquish 7SAYGDEEPF: positions 1–8 + 10–11The ambiguity scope observations post againstVerified

This record, posted across the family.

Every line is a posted fact at its own address.

The written record: pieces that touch this vin's questions.

The Reading Plan: open, scan, follow.

  1. 01Open: blogs.vin, the whole corpus on one page.
  2. 02Scan: newest first, grouped by pillar, each piece dated.
  3. 03Follow: the piece at its own door's /blog address; the door's record instrument is one paste away.
Distance to done: 3 stepsRead every door's pieces

For the agent you send.

The agent reads the same record you do.

Same two routes, three representations: the numbers never differ between them.

Three representationsblogs.vin/7SAYGDEE9PF947496
1curl https://blogs.vin/7SAYGDEE9PF947496 -H 'accept: application/json'
2 # the record as typed evidence objects
3curl https://blogs.vin/7SAYGDEE9PF947496 -H 'accept: text/markdown'
4 # the record's markdown twin
5curl https://blogs.vin/7SAYGDEE9PF947496
6 # this page
On this host
  • 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.

Every door, this record.

The same seventeen characters, read at every address.