specs.vin
apis.vin

The factory specifications.

Paste. Read. Compare.

The factory’s numbers for the car the VIN actually is — not the trim the ad claims. Reading the specifications is free. No account. Dimensions, powertrain, capacities, standard equipment — each line with its source.

Hand the VIN to an agent that works for you and it pulls these same numbers — nothing here needs your signature, and what it reads is what you read.

Specification sheetspecs.vin/7MMVABDM3RN163785
7MMVABDM3RN163785

7MMVABDM3RN163785

2024 Mazda CX-50

Mazda · WMI 7MMModel year 2024 · position 10Check digit 3 · verified

FACTORY SPECIFICATIONS · FOR THE TRIM THIS CAR IS

BODY STYLEposts live
DRIVETRAINposts live

POWERTRAIN

  • ENGINEposts live
  • DISPLACEMENTposts live
  • HORSEPOWERposts live
  • TORQUEposts live
  • TRANSMISSIONposts live

DIMENSIONS

  • LENGTHposts live
  • WIDTHposts live
  • HEIGHTposts live
  • WHEELBASEposts live

CAPACITIES

  • SEATINGposts live
  • CARGOposts live
  • FUELposts live
  • TOWINGposts live
  • PAYLOADposts live

STANDARD EQUIPMENT

  • EXTERIORposts live
  • INTERIORposts live
  • SAFETY & MECHANICALposts live

Figures render live at the address. This page states structure, not numbers.

every number posts with value · source · timestamp

How it reads.

  • 01PasteThe VIN, at specs.vin/{VIN}. Seventeen characters; the check digit verifies as you type — where the convention applies.
  • 02ReadThe VIN resolves to its year, make, model, and trim; the trim resolves to its factory numbers — dimensions, powertrain, capacities, standard equipment, each line with its source.
  • 03CompareThe ad’s claim against the record’s number. Where they differ, the delta is stated, not argued.
Postedspecs.vin fee: $0 per VIN · every VIN, every visit · no account
SourceEvery number posts with value · source · timestamp; where the factory record is unavailable: “Reported, not yet verified.”

The wrong-trim spec.

“Tows 10,000 lbs” is a brochure line about a trim. The record posts the number for this trim — before you pay a capability premium on equipment the car never carried.

Capability that came in on an option — a tow package, an off-road package — belongs to the as-built record, at sticker.vin. The spec is the car as designed; the sticker is the car as ordered. The seller reads the same page you do.

Questions with posted answers.

  • Are these the specs for my exact car?

    The VIN resolves to its year, make, model, and trim; the numbers post for that trim, source stated. Options that change capability live on the as-built record — sticker.vin.

  • What does it cost?

    $0, posted above like every other number.

  • The ad claims a number this page doesn’t show.

    Then the claim and the record differ — the delta is stated, not hidden. What the trim carries is on this page; what the seller added or asserts belongs to the ad, and the negotiation.

The spec is the first look.

The free faces of the record read the same seventeen characters — check them first. They cost what this page costs: $0.

free faces of the record · $0, posted

when the free faces raise a question · the record deepens

One spine of the catalog.

The specification is one spine of the record’s crosswalk: the VIN resolves to the YMMTS hierarchy — year, make, model, trim, style — and every other face of the record joins through it. The catalog behind this page is posted at the pillar door; this door owns one job: the factory numbers, free.

  • data.vinthe pillar catalog — every dataset behind this page: coverage, license, posted price
  • vindex.vinthe crosswalk — the YMMTS spine the spec rides, every provider’s IDs cross-mapped
  • specs.vin/7MMVABDM3RN163785this page — the sheet itself
  • apis.vinthe same numbers as typed JSON, one key
  • apis.vin/mcpone MCP server for the whole platform

An agent is a customer at this address on its own account — the motion is b2a.vin. Where an agent reads for a person, the receipt invariant holds: everything it does here survives being shown to them — the numbers it returns are the numbers on this page.

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

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