The work, ordered by the number.

services.vin is the Services layer’s one address: every physical job a car needs, sold in five lanes, quoted from its VIN, ordered on one chassis, settled on one invoice. Vendor cost and our margin post as separate lines on every order. The quote is free. No account.

2025 Mazda CX-5 · check digit 1 · verified

JM3KFBXY1S0597748

2025 Mazda CX-5

  • ServiceMobile pre-purchase inspection
  • Attached toThe open deal · settles on the parent invoice
  • Vendor costPosts live
  • Our marginPosts live
Total · computed at orderPosts at order

Order id, timestamps and amounts render live at the address. Structure, not samples.

Move.

The car moves.

Long haul, last mile, the border crossing, the breakdown. Every move quotes from the VIN and two zips: the decode supplies what the dispatcher would have asked on the phone.

One shipment, two zipstransport.vin
Origin ZIPDestination ZIP2025 Mazda CX-5
  1. Quote
  2. Track
  3. Delivered
  • DeliveredTo the door of the buyertransport.vin
  • TitleTitle status read from the recordtitle.vin
  • In transitTracked by the VINtransport.vin
  • InspectionThe condition report posts to the recordinspection.vin
  • QuoteTwo zips produce the quotetransport.vin
The lane

transport.vin is this lane’s flagship: the move is its own order, at its own address, never re-quoted here.

Fix.

The work on the car itself.

Cash mechanical, insurer-paid collision, the diagnostic read, the finish: four addresses, one work order. A completed fix posts its facts to the record.

Inspection and recon run as one unit: the finding drives the work order.

Paper.

One office visit, two doors, one chassis.

Title and registration are co-canonical peers: the rare transfer and the annual renewal each hold their own address and ride the same order. Emissions is the third paper: the state-regulated test whose pass or fail posts as a fact.

Where a state’s gate has not cleared, the row reads “not yet offered in that state”: a fact, stated.

Keep.

The car, kept.

Scheduled service by the book, the month of storage, the keeping surface itself. The keep lane is the record’s slow lane: recurring, quiet, attached to the same seventeen characters.

Power.

The act of charging is Services.

The state of the battery is Data: state-of-health reads at the record, per report, like an odometer. The command stays in this lane; the query exits to the catalog. That line is the lane.

One chassis.

Quote, paid order, webhook, one invoice, deal-attached. Every lane sells through the same four hops.

The quote posts from the VIN, free. The paid order opens at the posted price with vendor cost and our margin as separate lines. Webhooks post distance-to-done. An order attached to an open deal settles under the parent invoice’s one total.

  1. 01Quote

    Free · from the VIN

    Every lane prices from the decode: vendor cost and margin itemized before any commitment.

  2. 02Paid order

    Timestamp posts as it clears

    The order opens at the posted price. service.created posts to the record.

  3. 03Webhook

    Posts as it changes

    Vendor status posts as it changes: service.updated, then service.completed with the completion facts. Distance-to-done is a line on the record, not a phone call.

  4. 04One invoice

    Posts at settlement

    A deal-attached order settles under the parent invoice’s one total at buy.vin; the move’s line settles at transport.vin, the member that owns it.

Order id, timestamps and amounts render live at the address. Structure, not samples.

One VIN, one order record per job, one invoice per deal.

Order from a lane

Not yet open · vendor papering per service cluster + per-state title/reg fulfillment gate before orders

Order actions render through the compliance gate. Vendor agreements per service cluster and the per-state title and registration gate are in progress; until they clear, nothing on this page takes a paid order. The quote is live today: every job prices from the VIN, free, no account.

The seams.

Some facts read in another layer.

  • Battery · batteries · SOHThe health is a record fact; it reads in the Data layer at data.vin.
  • Warranty · warrantiesThe VSC sale books in Commerce at fi.vin; the covered-repair claim is a fix-lane order here.
  • Accessories · partThe thing is Commerce, the fitment is Data; only the install is a Services act.
  • EscrowSettlement is Commerce; this layer cross-references, never claims escrow.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 representationsservices.vin
1curl https://services.vin/ -H 'accept: text/markdown'
2 # the markdown twin of this page
3curl https://services.vin/{VIN} -H 'accept: application/json'
4 # the record as typed evidence objects
5curl https://services.vin/{VIN} -H 'accept: text/markdown'
6 # the record's markdown twin
On this host
  • Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the callb2a2cAn agent acting for a consumer: everything it does survives being shown to them afterward
  • 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.