The charging face · POWER lane · Services
The charging act, dispatched from the VIN.
Quote. Charge. Posted.
One VIN opens the work — the fleet and the driveway on one record. The decode says what the car takes, so the driveway install quotes in writing from the VIN and a zip; on the road, sessions post with dates and energy — the electric car’s service history. Quotes are free. No account.
Hand this record to your agent: it walks the quote and the sessions, and you appear only where you’re load-bearing — authorize the install, authorize any revision, in writing.
A VIN is 17 characters and never uses I, O, or Q.
The battery is a Data fact
state of health · reads at the record, per reportlike an odometer — the fact reads in the Data layer; the act of charging quotes and orders here
The install quote, as it posts
- vendor cost— posted as its own line
- our margin— posted beside it, never inside it
- total— the number you pay, in writing
- the basis— what the quote priced, stated with it
the session line posts beside it — the session · the date · the energy — the record the installer sees too
Figures render live at the address. This page states structure, not prices.
The battery is Data; the act is Services.
The state of the battery is a record fact — state of health reads at the record, per report, like an odometer, in the Data layer at data.vin. Nothing on this page sells you a reading.
The act of charging is work the car needs: it quotes, orders, and invoices here, on the services chassis — the install in writing, the session with its date and energy.
The command stays in this lane; the query exits to the catalog. That line is the lane.
The seambattery · state of health — record facts, read in the Data layer
The driveway — the install, quoted in writing.
The open-wall estimate is the desk’s local franchise here — the number that appears after the electrician leaves. Here is what posts instead.
- What does the car take?the decode says: the powertrain and the connector the build reports — what the installer would have asked
- What does the install cost?the written quote: vendor cost · our margin · total as separate lines, with its basis
- Which wall, which panel?the zip opens the market; the site facts post on the order before the work
- What if the wall needs more?a finding posts as a written revision you authorize before the work continues, never a number at the end
Everything the sheet knows, it posts. Everything it asks, it needed. The installer sees this exact page.
The road — sessions on the record.
Your charging network account connects at connects.vin — sessions post with dates and energy, the electric car’s service history on one record. No network is named on this page; the account class is, and yours stays yours.
A fleet runs the same rail per VIN list: depot charging ordered per unit, each session posting to its own record, vendor cost and margin per line.
An electric car’s service history is its sessions — posted, it is a fact the next buyer can read.
the session · the date · the energy · posted to the record
The order, on the services chassis.
Quote → order → posted. The order transacts through the services.vin counter — one VIN, one order, one invoice.
01Quotelive today · free
Paste the VIN and the zip. The decode says what the car takes; the written quote posts with its basis through the services.vin counter — vendor cost and our margin as separate posted lines.
the vendor cost · our margin · the total
02Orderopens when the gate clears
Pay the posted price; the order opens at the address — the driveway install or the depot list. A site finding posts as a written revision and waits — authorized before the work continues, never a number at the end.
the order · the revisions · the authorization
Order the installnot yet open · installer papering and per-state kWh-metering and resale rules verified for the charging cluster before paid installs or sessions
The order action renders through the compliance gate: installer papering and per-state kWh-metering and resale rules run through the services.vin chassis; until they clear, nothing on this page takes a paid order or starts a paid session. The written quote is live today — free, no account.
03Postedposts to the record
Each session posts with its date and energy; the completion posts to the record, the invoice line beside it. Our margin posts per order as its own line — no fee appears at settlement that wasn’t on the quote.
the session · the completion · the invoice line
Order id, timestamps, and amounts render live at the address. Structure, not prices.
Who charges.
One posted quote, three registers — the same lines, the same timestamps.
The driveway
A new EV and no number for the install
Today the number arrives after the wall is open. Here the quote posts in writing from the VIN and the zip, and every revision waits for a written yes.
sticker.vinwhat the car takes, as built
Quoted in writing · authorized before the work
The road
Sessions scattered across apps
The connected account posts them to one record — dates and energy, the electric car’s service history, readable when it matters: at the sale.
The fleet
Depot charging, per VIN list
Depot charging bulk-orders per VIN list at net terms — vendor cost and margin post per line, per unit, each session on its own record.
Reading the battery rather than charging it? State of health is a record fact — it reads in the Data layer at data.vin. This door orders the work.
The charging line is one face of the record.
If an agent orders the charging for you, it reads this same record: the written quote · the posted sessions · 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://charge.vin/ -H 'accept: text/markdown' → the markdown twin of this page
curl https://charge.vin/{VIN} -H 'accept: application/json' → the record as typed evidence objects
curl https://charge.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.
