The dispatch face · MOVE lane · Services
Roadside help, dispatched from the VIN.
Request. Dispatched. Done.
One VIN and one zip open the incident: the decode supplies year, make, model, and drivetrain — what the dispatcher would have asked on the phone — and the price posts with its basis before any truck rolls. At dispatch the provider is named on the record, its ETA beside it. Quotes are free. No account.
Hand this record to your agent: it walks the quote and the dispatch, and you appear only where you’re load-bearing — name the incident, authorize the dispatch, in writing.
A VIN is 17 characters and never uses I, O, or Q.
Named at dispatch
the provider · the ETAthe truck that arrives is the one named on this record — never an anonymous chain
The posted price, as it posts
- provider cost— posted as its own line
- our margin— posted beside it, never inside it
- total— the price on the hook, posted before the truck rolls
- the basis— what the price covers, stated with it
reads beside decode · odometer · recalls — the record the provider sees too
Figures render live at the address. This page states structure, not prices.
Six incidents, one record.
Every incident is the same shape on the wire: named, priced, dispatched, done — each fact posted with its timestamp.
- towthe hook and the destination post before the truck rolls; a tow that becomes a move rides the transport rail
- lockoutthe door opened against the record that says whose car it is
- jump starta jump that will not hold is a finding — it posts to the record, and the repair quotes from it
- fuelenough to reach the pump, priced before the truck rolls
- tire changethe spare mounted — or the tow posted honestly when there is no spare
- winchoff the soft shoulder; recovery stated as its own line, never a surprise on the hook
A tow that becomes a move — the auction win, the season’s end — rides the scheduled rail at transport.vin. This door clears incidents.
The price, before the truck rolls.
The hook fee is the desk’s local franchise here — the number that appears once the car is on the truck and cannot leave. Here is what posts instead.
- What car is it?the decode, posted from the VIN: year, make, model, drivetrain — what the dispatcher would have asked
- Where is the car?the zip names the spot; the exact curb posts on the order
- What happened?the incident named: tow · lockout · jump start · fuel · tire change · winch
- What does it cost?the posted price: provider cost · our margin · total as separate lines, with its basis
- When does the truck arrive?the ETA posts at dispatch and updates as the truck moves
Everything the sheet knows, it posts. Everything it asks, it needed. The provider sees this exact page.
The dispatch, on the services chassis.
Request → dispatched → done. The order transacts through the services.vin counter — one VIN, one order, one invoice.
01Requestlive today · free
Paste the VIN and the zip, name the incident. The decode supplies year, make, model, and drivetrain; the price posts with its basis through the services.vin counter — provider cost and our margin as separate posted lines.
the provider cost · our margin · the total
02Dispatchedopens when the gate clears
Pay the posted price; the provider is named on the record with the ETA beside it. The price that posted is the price on the hook — a recovery condition posts as its own written line, never a number at the curb.
the provider · the ETA · the destination
Dispatch the trucknot yet open · motor-club registration per state and provider papering for the incident-dispatch pool before paid dispatch
The dispatch action renders through the compliance gate: motor-club registration per state and provider papering for the incident-dispatch pool run through the services.vin chassis; until they clear, nothing on this page dispatches a truck. The quote is live today — free, no account.
03Doneposts to the record
Status posts distance-to-done as the truck moves; the completion posts to the record, timestamped, the invoice line beside it. Our margin posts per incident as its own line — no fee appears at dispatch that wasn’t on the quote.
the status · the completion · the invoice line
Order id, timestamps, and amounts render live at the address. Structure, not prices.
Who calls for help.
One posted price, three registers — the same lines, the same timestamps.
The driver
Stopped now, hazards on
Today the number firms up on the hook. Here the price posts before the truck rolls, and the truck that arrives is the one named on the record.
recalls.vina stall can be a campaign — check the free repair
Priced before the truck rolls · the provider named
The household
The second car, the kid’s first car
“Who towed it, and where” is answered by the record — a name, a destination, a timestamp — not a memory the next morning.
The fleet
A unit down on a route
Dispatch per VIN at net terms — provider cost and margin post per line, per unit. The route learns the ETA the moment the record does.
Planning the move rather than surviving it? The scheduled haul is the sibling lane at transport.vin. This door clears incidents.
The incident is one face of the record.
If an agent calls for help on your behalf, it reads this same record: the posted price · the named provider · the completion on the record is the receipt that survives being shown to you — tools at apis.vin/mcp.
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 · B2A2C
- B2A — the buyer is an agent — no human leaf; discover, bind, pay, worst-case cost posted before the call
- B2A2C — an agent acting for a consumer — everything it does survives being shown to them afterward
curl https://roadside.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://roadside.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://roadside.vin/{VIN} -H 'accept: text/markdown' → the record's markdown twinMachine surfaces on this host: /llms.txt · /icp.json · /.well-known/agents.json · one MCP server for the whole platform — 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.
