blogs.vin/JM3KFBXY1S0597748
2025 Mazda CX-5.
What the platform has written.
JM3MakerKFBXYVehicle1CheckSYear0597748This car
Σ value × weight = 386 ·386 mod 11 = 1 · position 9 reads 1
Decoded from VINSample record2026-07-04 13:27Check digit validBoth parties see this exact record
Any VIN, one address
The build, decoded
- BodySUVSample recordPosted 2026-07-04 13:27Verified
- DrivetrainAWDSample recordPosted 2026-07-04 13:27Verified
- Engine2.5L I4 TurboSample recordPosted 2026-07-04 13:27Verified
What the seventeen characters certify
- Check digitPosition 9 reads "1": the other sixteen compute "1"ISO 3779 · 49 CFR 565.15(c) check-digit mathVerified
- Validation regimePrimary identity is not the VIN: validated structurally · Japan (ISO 3780 J block)MLIT/NALTEC regime: domestic identity is katashiki + frame number; 17-char VINs mainly on exports (vindex market registry, JP row)Verified
- Manufacturer idWMI JM3: positions 1–3ISO 3779 VIN structureVerified
- Model-year codePosition 10 reads "S": the 2001–2030 code table reads 2025ISO 3779 model-year tableVerified
- PatternSquish JM3KFBXYS0: positions 1–8 + 10–11The ambiguity scope observations post againstVerified
This record, posted across the family.
Every line is a posted fact at its own address.
The written record: pieces that touch this vin's questions.
The Reading Plan: open, scan, follow.
- 01Open: blogs.vin, the whole corpus on one page.
- 02Scan: newest first, grouped by pillar, each piece dated.
- 03Follow: the piece at its own door's /blog address; the door's record instrument is one paste away.
Distance to done: 3 stepsRead every door's pieces
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 representations
1curl https://blogs.vin/JM3KFBXY1S0597748 -H 'accept: application/json'
2 # the record as typed evidence objects
3curl https://blogs.vin/JM3KFBXY1S0597748 -H 'accept: text/markdown'
4 # the record's markdown twin
5curl https://blogs.vin/JM3KFBXY1S0597748
6 # this page
On this host
- Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the call
- Machine surfaces/llms.txt/icp.json/.well-known/agents.json
- 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.
Every door, this record.
The same seventeen characters, read at every address.
- The pillars
- data.vinThe record layer's own door: every dataset behind the platform's pages, cataloged.
- services.vinCar services ordered by the VIN: the catalog the Services pieces write about.
- commerce.vinThe whole deal as one order: the settlement layer the Commerce pieces write about.
- The family
- vin.companyEvery door, one record: vin.company/JM3KFBXY1S0597748