7MM·VABDM3·RN163785

2024 Mazda CX-50 Preferred — the inspection

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

vehicle2024 Mazda CX-50 Preferred · decoded from VIN · SUV · FWD · 1.5L I4 Turbo · posted 2026-07-04 17:09 · verified

odometer27,627 mi · consistent across 15 records · posted 2026-07-04 · verified

recallsNo open recalls · recall registry · posted 2026-07-04 · verified

This record, posted across the family

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 · B2H2A

B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
B2H2A — the human appears once, where the act is legally load-bearing — then the agent resumes

curl https://inspection.vin/7MMVABDM3RN163785 -H 'accept: application/json'   → the record as typed evidence objects
curl https://inspection.vin/7MMVABDM3RN163785 -H 'accept: text/markdown'      → the record's markdown twin
curl https://inspection.vin/7MMVABDM3RN163785                                 → this page

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.

Every door, this record

know the car

vhr.vinWhat the paper says before the inspector looks: the history for 7MMVABDM3RN163785
values.vinCondition moves the number: five values for 7MMVABDM3RN163785, posted

the counter

services.vinThe order transacts at services.vin — one VIN, one order, one invoice

do the deal

buy.vinBuying remote? The inspection attaches to the deal at buy.vin/7MMVABDM3RN163785
transport.vinIt passed: the move quotes from 7MMVABDM3RN163785 and two zips