The move face · Move lane · Services

Ship any car with a VIN and two zips.

Quote.Track.Delivered.

The move runs as a custody chain: five events, each posted to one record with its timestamp. The price before anything moves, the carrier by name, photos at both handoffs. The quote is free. No account.

Hand this record to your agent: it walks the quote and the tracking, and you appear only where you’re load-bearing: authorize the move, sign at pickup and delivery.

Custody recordtransport.vin/JM3KFBXY1S0597748

JM3KFBXY1S0597748

2025 Mazda CX-5

From94103
To10001
ModeLong haul · last mile · valet · towPosts on quote

01QuoteFree · posts today
02BookedOpens when the gate clears
03Picked upTimestamp posts at pickup
04In transitPosts as the car moves
05DeliveredTimestamp posts at delivery

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

The custody chain.

Quote, booked, picked up, in transit, delivered.

Five events, each one posted to the record: who holds the car, what it costs, what it looked like, with a timestamp beside it.

01Quote
Free · posts today
The decode supplies dimensions and operability, so the price is computed, not guessed: nobody calls to confirm details. It posts with its rate basis and ETA, the carrier rate and our broker margin as separate lines.
The carrier rate · the broker margin · the total
The rate basis · the ETA
02Booked
Opens when the gate clears
The carrier is named on this record at booking: the rate we pay them and the margin we keep, with the pickup window. One handoff, posted; no re-brokering chain.
The carrier · the pickup window · the total
Book the move
Not yet open · MC broker authority + BMC-84 before bookings; quotes stay free
This action renders through the compliance gate. Broker authority and the surety bond are in progress; until they clear, nothing on this page books a move. The quote is live today: price, rate basis and ETA post free at the address.
03Picked up
Timestamp posts at pickup
Custody transfers to the named carrier at your curb. Pickup photos post to this record, each with a timestamp, before the car moves.
The photo set · custody · the named carrier
04In transit
Posts as the car moves
Position and distance-to-done post as the car moves. Where the car is, is a line on the record, not a call to dispatch.
The miles to done · the last posted time
05Delivered
Timestamp posts at delivery
Delivery photos post before you sign. A finding new since pickup is stated on the record, timestamp against timestamp, and routes to the carrier’s cargo coverage.
The photo set · signed, with its timestamp

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

Three fields are the whole intake.

The phone call exists to ask what the record already knows.

The decode answers it.

Year, make, model?The decode: posted from the VIN
Dimensions and weight?The decode: the build says so
Does it run?Operability posts from the record; a tow rides anyway
Open or enclosed truck?Mode posts on the quote: long haul, last mile, valet, tow
What does it cost?The posted price: carrier rate and margin as separate lines

Everything the sheet knows, it posts. Everything it asks, it needed.

The middle, posted.

Between pickup and delivery is where the old move goes quiet.

The car posted to a load board, re-brokered, the price revised at pickup, a driver’s phone number as the only status. This page is built against that middle. Every hop above is an event that posts (who holds the car, what it costs, what it looked like) with a timestamp beside it.

Four modes, one order record

Long haulThe cross-country move, tracked to the door.
Last mileAuction lot or rail head to the driveway.
ValetA driver, in the car, for the short hop.
TowThe car that doesn’t run rides anyway: the decode already said so.

Posted

PostedThe quote: free · every VIN, every lane, every visit · no account
The marginBroker margin posts per move as its own line beside the carrier rate: the rate we pay and the margin we keep, both on the sheet before any decision.
AgentsThe same record as typed JSON at the same address, via Accept negotiation; tools at apis.vin/mcp.

All four post to the same order record. One chain, whichever way the car rides.

Who holds the car, at every hop.

Custody is the question the middle usually swallows.

Here it is a column on the record, posted beside the money.

Hop	The car	The record	The money
Quote 01	You: keep driving it	Price · rate basis · ETA post	None moves: the quote is free
Booked 02	You, until the pickup window	Carrier named · rate and margin posted	The posted price: the quote is the price
Picked up 03	The named carrier	Pickup photos post, timestamped, before the car moves	Unchanged: no pickup-day revision
In transit 04	The same carrier: one handoff, posted	Distance to done posts as it moves	Unchanged
Delivered 05	In the driveway	Delivery photos post before you sign	Settled at the posted price

The price that posts at the quote is the price at every later hop. A delta exists only if operability or dimensions differ from what the decode reported: posted, signed, and sourced before you pay, never at the curb.

The driveway side

One car, somewhere else

Out-of-state purchase, the snowbird lane, an auction win: the car exists and the driveway is far away. This record is the move: quote from the VIN and two zips, then five posted hops to the door.

The posted quote · the ETA

The store side

Inventory on the same chain

A store’s transfer rides the same rail, and the delivery your customer sees is posted, not promised. Dealer moves read differently.

dealers.vinYour entrance to the store rails

The lane · the pickup window

Questions with posted answers.

Can I book a move today?

Not yet. Motor-carrier broker authority and the BMC-84 surety bond are in progress; the book action posts on this record the day they clear. The quote is live today: paste a VIN and two zips above, and the price posts with its rate basis and ETA, free, no account.

Is the quote the final price?

When booking opens, the posted quote is the booking price. If operability or dimensions differ from what the decode reported, the delta posts (signed and sourced) before you pay, never at pickup.

Who actually carries the car?

One carrier, named on the order record at booking, with the rate we pay them and the margin we keep beside it. One handoff, posted; no re-brokering chain.

What if the car is damaged in transit?

Pickup photos post with timestamps before the car moves; delivery photos post before you sign. A finding new between the two is stated on the record and routes to the carrier’s cargo coverage: the record settles it, not memory.

Moving more than one car?

Each VIN rides its own custody record: one chain per car, side by side. A store moving inventory reads the same rail through dealers.vin.

How does transport.vin make money?

Broker margin, posted per move as its own line beside the carrier rate. No fee appears at booking that wasn’t on the quote.

The third reader.

Humans read this page; agents read the same record, typed.

Every hop on the chain (quote, booked, picked up, in transit, delivered) is an object with a source and a timestamp, at the same address: the page at transport.vin/{VIN}, the JSON at the same address via Accept, the tools at apis.vin/mcp.

The chain, as an agent reads itapis.vin/mcp

1// tools/call · transport_quote

3 "type": "vin.transport.custody",

4 "vin": "JM3KFBXY1S0597748",

5 "chain": [

6 { "event": "quote", "total": <integer, USD cents>,

7 "posted": <RFC 3339 timestamp> },

8 { "event": "booked", "carrier": <named at booking>,

9 "posted": <RFC 3339 timestamp> },

10 { "event": "picked_up", "photos": <posted set>,

11 "posted": <RFC 3339 timestamp> },

12 { "event": "in_transit", "to_done": <miles>,

13 "posted": <RFC 3339 timestamp> },

14 { "event": "delivered", "photos": <posted set>,

15 "posted": <RFC 3339 timestamp> }

16 ]

17}

The motions this door serves

b2a.vinAn agent orders the move on its own account.
b2a2b.vinAn agent-brokered move rides this same sheet: the brokering fee posts as its own line, disclosed beside the carrier rate and the margin.
Evidence
Every event posts with source and timestamp: the chain replays in order.
Quotes read free at the address; booking obeys the same posted gate as this page.
One MCP server for the whole platform: apis.vin/mcp.

The move is one face of the record.

The other addresses read the same seventeen characters.

If an agent arranges the move for you, it reads this same record: the posted quote · carrier · margin · photo chain is the receipt that survives being shown to you.

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 representationstransport.vin

1curl https://transport.vin/ -H 'accept: text/markdown'

2 # the markdown twin of this page

3curl https://transport.vin/{VIN} -H 'accept: application/json'

4 # the record as typed evidence objects

5curl https://transport.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 callb2a2bAgents 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.