escrow.vin/JM3KFBXY1S0597748
2025 Mazda CX-5 2.5 Turbo Signature.
The escrowed funds.
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
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
The market read: under seal
- Retail and trade figures
- Comparable transactions, counted
- The valuation band, dated
This record, posted across the family.
Every line is a posted fact at its own address.
The escrowed funds for this vin.
The Held-Funds Plan: look up, read, settle.
- 01Look up: a VIN at escrow.vin/{VIN}; the deal's funds face assembles from the record.
- 02Read: held balance, release conditions, and settlement events, each posted with source and timestamp.
- 03Settle: inside the one order at buy.vin/{VIN}; the release posts back to this record as an event. You are 1 step from the close.
Distance to done: 3 stepsSettle inside the one order: buy.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.
Three representations
1curl https://escrow.vin/JM3KFBXY1S0597748 -H 'accept: application/json'
2 # the record as typed evidence objects
3curl https://escrow.vin/JM3KFBXY1S0597748 -H 'accept: text/markdown'
4 # the record's markdown twin
5curl https://escrow.vin/JM3KFBXY1S0597748
6 # this page
On this host
- Motionsb2a2cAn agent acting for a consumer: everything it does survives being shown to them afterwardb2a2bAgents brokering between businesses: Mandate presented, fee disclosed, settlement three-way
- 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.
- Do the deal
- buy.vinSettlement runs inside the one order at buy.vin/JM3KFBXY1S0597748: the release posts back here
- The order
- commerce.vinThe transaction layer: every line of the deal at its own address, one total
- Fund the deal
- financing.vinThe financed portion lands in the same held balance: rates posted for JM3KFBXY1S0597748
- Deliver
- transport.vinRelease can condition on delivery: transport posts the delivered event for JM3KFBXY1S0597748