# maintenance.vin
> The factory maintenance schedule for any VIN — interval by interval from the decode and posted specs — and the work, ordered at a posted price, posted to the record when done.

The maintenance schedule for any VIN, interval by interval, each item with its source — derived from the decode and posted specs, so a "recommended" list is checkable against the book. The schedule is free. No account. Ordered work posts its completion to the record.

Motions: B2A · B2A2C
Routes: GET / (this document's page) · GET /{VIN} (the record for one vehicle)
Representations: text/html · text/markdown · application/json (Accept header; same URL)
Evidence: every field posts value · source · timestamp · verification state; empty states are typed EMPTY, invalid VINs are typed INVALID_VIN — never a faked 200.
Agent surface: one estate MCP server — https://apis.vin/mcp (all .vin doors are lenses over one spine; tools: decode_vin, vehicle_history, market_value, window_sticker, out_the_door_price, open_recalls, search_listings, cash_offer, transport_quote, finance_prequal, insurance_quote, start_purchase)
Gates: typed OFFER (posted price, hard ceiling, x402) or NEEDS_HUMAN handoff URL — no account walls.
Auth: https://auth.vin (issuer) · keys/metering via id.org.ai
Siblings:
https://services.vin/ — Due work is orderable — every job on any VIN quoted from one record at services.vin
https://recalls.vin/ — An open campaign posts beside the schedule — the manufacturer's work, free at the dealer
https://vhr.vin/ — What the car has actually had done: the posted history for any VIN
https://values.vin/ — A kept schedule meets the number: five values for any VIN, posted