# charge.vin
> EV charging from the VIN — the install quoted in writing, the session posted with its date and energy, the charging line on the record.

The charging act, dispatched from the VIN — the fleet and the driveway on one record. The decode says what the car takes; the driveway install quotes in writing from a VIN and a zip; sessions post with dates and energy — the electric car's service history. The state of the battery is a Data fact and reads at the record; the act of charging quotes, orders, and invoices here. Quotes are free. No account.

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 MCP server for the whole platform — 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/