build.vin
Become a Partner
WP0·AA2A92·PS206106

2023 Porsche 911 Carrera — the build record

decoded from VIN · sample record · 2026-07-11 12:34 · check digit valid · both parties see this exact record

the build, decoded

bodyCoupe · sample record · posted 2026-07-11 12:34 · verified
drivetrainAWD · sample record · posted 2026-07-11 12:34 · verified
engineElectric · sample record · posted 2026-07-11 12:34 · verified

what the seventeen characters certify

check digitposition 9 reads "2" — the other sixteen compute "2" · ISO 3779 · 49 CFR 565.15(c) check-digit math · verified
validation regimecheck digit not mandated — validated structurally · Europe (ISO 3780 S–Z block) · Commission Regulation (EU) No 19/2011 (VIN requirements, no check-digit mandate); ISO 3779:2009; GB: Assimilated Regulation (EU) No 19/2011 · verified
manufacturer idWMI WP0 — 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 WP0AA2A9PS — positions 1–8 + 10–11 · the ambiguity scope observations post against · verified

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

the history — under seal

  • title chain and brand events
  • odometer records
  • owner count
  • open campaign status
sign in — $0 posted

the market read — under seal

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

This record, posted across the family

the as-built face — this vin as the factory ordered it

The As-Built Plan — paste, trace, carry.
  1. Paste — the VIN, at build.vin/{VIN}.
  2. Trace — the claim to the factory order: what the OEM record holds for this car, section by section, with plant and build date posted.
  3. Carry — the record into the appraisal, the ad, or the negotiation; the printed document is one door away at sticker.vin/{VIN}.
distance to done: 3 steps

read the build record — options, packages, plant, build date

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

Know the car
  • sticker.vinThis record, printed: the window sticker for WP0AA2A92PS206106 as the factory shipped it.
  • vhr.vinThe build is day zero. The owners, titles, and odometers of WP0AA2A92PS206106 follow.
  • values.vinWhat this build is worth today, options included — posted with its basis.
The data layer
  • data.vinThe pillar door: every dataset behind this page, cataloged — coverage, license, price, posted.
The family
  • vin.companyEvery door, one record: vin.company/WP0AA2A92PS206106