values.vin
7SA·YGDEE9·PF947496

2023 Tesla Model Y Long Range AWD — the value

decoded from VIN · sample record · 2026-07-17 10:04 · check digit valid · both parties see this exact record

the build, decoded

bodySUV · sample record · posted 2026-07-17 10:04 · verified
drivetrain4WD · sample record · posted 2026-07-17 10:04 · verified
engine5.0L V8 · sample record · posted 2026-07-17 10:04 · verified

the market face

listed$9,748 · live listing · posted 2026-07-17 · verified

what the seventeen characters certify

check digitposition 9 reads "9" — the other sixteen compute "9" · ISO 3779 · 49 CFR 565.15(c) check-digit math · verified
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 VIN · reported, not yet verified
manufacturer idWMI 7SA — positions 1–3 · ISO 3779 VIN structure · verified
model-year codeposition 10 reads "P" — the 2001–2030 code table reads 2023 · ISO 3779 model-year table · verified
patternsquish 7SAYGDEEPF — positions 1–8 + 10–11 · the ambiguity scope observations post against · verified

under seal — the free rows above are real and stay free

the market read — under seal

  • retail and trade figures
  • comparable transactions, counted
  • the valuation band, dated
sign in — $0 posted

the rest of this record is under seal — the free rows above are real and stay free

fee posted

$0

sign in

identity is the posted price · account issued by auth.vin

at sign-in

  • the full comp table, every row — free at login for humans, forever
  • per-comp detail and cost-to-own depth

the check digit certifies; it never sells

This record, posted across the family

the value face — five bands for this vin

The Five Numbers Plan — paste, read five, take one.
  1. Paste — the VIN, at values.vin/{VIN}. One question if the trim is ambiguous.
  2. Read five — retail, private party, trade, wholesale, auction, each posted with source and timestamp; comps attached.
  3. Take one — to offers.vin to sell it, or vhr.vin to see why it's priced there.
distance to done: 3 steps

turn this number into cash — offers.vin/{VIN}

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://values.vin/7SAYGDEE9PF947496 -H 'accept: application/json'   → the record as typed evidence objects
curl https://values.vin/7SAYGDEE9PF947496 -H 'accept: text/markdown'      → the record's markdown twin
curl https://values.vin/7SAYGDEE9PF947496                                 → this page

Machine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one MCP server for the whole platform — 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 platform return a typed OFFER (posted price · hard ceiling) or a NEEDS_HUMAN handoff, never a dead end.

Every door, this record

Do the deal
  • offers.vinSell it: offers against the trade and wholesale bands, posted.
  • financing.vinFinance at the retail band: rate posted, not teased.
  • buy.vinBuy: the listing posted with timestamp · 7-step checklist close.
Know the car
  • vhr.vinHistory: records posted for 7SAYGDEE9PF947496 · the history says why, or it doesn't.
Every door
  • vin.companyEvery door, one record: vin.company/7SAYGDEE9PF947496