specs.vin
Become a Partner
1GN·SKRKD5·MR488605

2021 Chevrolet Malibu Base — the factory specifications

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

the build, decoded

bodyHatchback · sample record · posted 2026-07-03 15:17 · verified
drivetrainRWD · sample record · posted 2026-07-03 15:17 · verified
engine1.5L I4 Turbo · sample record · posted 2026-07-03 15:17 · verified

what the seventeen characters certify

check digitposition 9 reads "5" — the other sixteen compute "5" · ISO 3779 · 49 CFR 565.15(c) check-digit math · verified
validation regimecheck digit enforced — United States (ISO 3780 1/4/5 block) · 49 CFR 565.15(c) / FMVSS No. 115 · verified
manufacturer idWMI 1GN — positions 1–3 · ISO 3779 VIN structure · verified
model-year codeposition 10 reads "M" — the 2001–2030 code table reads 2021 · ISO 3779 model-year table · verified
patternsquish 1GNSKRKDMR — 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

the spec face — this vin's factory numbers

The Spec Plan — paste, read, compare.
  1. Paste — the VIN, at specs.vin/{VIN}.
  2. Read — the factory numbers for the trim this car is: dimensions, powertrain, capacities, standard equipment, each line with its source.
  3. Compare — the ad's claim against the record's number. You're 0 steps from done; where they differ, the delta is stated, not argued.
distance to done: 3 steps

read the specifications — dimensions, powertrain, capacities, equipment

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://specs.vin/1GNSKRKD5MR488605 -H 'accept: application/json'   → the record as typed evidence objects
curl https://specs.vin/1GNSKRKD5MR488605 -H 'accept: text/markdown'      → the record's markdown twin
curl https://specs.vin/1GNSKRKD5MR488605                                 → 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.vinAs designed is this page; as ordered is the sticker — options and packages for 1GNSKRKD5MR488605, retrieved.
  • vhr.vinThe spec says what it is; what happened to 1GNSKRKD5MR488605 is the history — posted.
  • values.vinWhat this spec is worth today — the posted numbers and their 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/1GNSKRKD5MR488605