garage.vin/7SAYGDEE9PF947496

2023 Tesla Model Y Long Range AWD.
The keeping face.

Σ 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 addressgarage.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

The membership row: what stands on this VIN

What the garage is designed to hold about this VIN. The standing acts live on the one Vin account: the shape of the keeping, not your findings.

  • The watchArmed or not, per VIN: the standing recall watch; its home door is recalls.vinNot yet open · the one Vin account opens first: auth.vin
  • The savesWhich faces you kept on this VIN: the checks that survive the visitNot yet open · the one Vin account opens first: auth.vin
  • The entitlementsThe report you bought, held on the record: designed to stay openNot yet open · the one Vin account opens first: auth.vin

This record, posted across the family.

Every line is a posted fact at its own address.

The keeping face: what the garage holds about this VIN.

The Keeping Plan: paste, keep, return.

  1. 01Paste: one VIN opens the keeping face: what the garage can hold about this car, each face linked to its live sibling door. Free, no account.
  2. 02Keep: the standing acts on the one Vin account: the VIN saved to your garage, the recall watch armed, the report you bought held on the record. Opens with auth.vin.
  3. 03Return: the second visit starts where the first one ended: the watches standing, the saves in place, the bought report open on the same seventeen characters.
One step live today · two open with the accountRun the recall check at recalls.vin: the watch's home door, free

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 representationsgarage.vin/7SAYGDEE9PF947496
1curl https://garage.vin/7SAYGDEE9PF947496 -H 'accept: application/json'
2 # the record as typed evidence objects
3curl https://garage.vin/7SAYGDEE9PF947496 -H 'accept: text/markdown'
4 # the record's markdown twin
5curl https://garage.vin/7SAYGDEE9PF947496
6 # this page
On this host
  • Motionsb2h2aThe human appears once, where the act is legally load-bearing; then the agent resumesb2a2cAn agent acting for a consumer: everything it does survives being shown to them afterward
  • 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.