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.
JM3KFBXY1S0597748
2025 Mazda CX-5
- What the car takesPosted from the decode
- Where the wall is94103
The battery is a Data factdata.vin
State of health · reads at the record, per report
Like an odometer: the fact reads in the Data layer; the act of charging quotes and orders here.
- The install quote, as it posts
- Vendor costPosted as its own line
- Our marginPosted beside it, never inside it
- TotalThe number you pay, in writing
- The basisWhat 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. The act of charging is work the car needs.
Nothing on this page sells you a reading. The install posts in writing; the session posts with its date and energy.
- State of healthReads at the record, per report, like an odometer.
- Where it readsIn the Data layer at data.vin, beside the decode.
- On this pageNothing sells you a reading.
- The installQuoted in writing from the VIN and the zip.
- The sessionPosted with its date and energy.
- Where it runsHere, on the services chassis: it quotes, orders and invoices.
The command stays in this lane; the query exits to the catalog. That line is the lane.
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. Everything the sheet knows, it posts. Everything it asks, it needed. The installer sees this exact page.
- 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.
The road: sessions on the record.
An electric car’s service history is its sessions: posted, it is a fact the next buyer can read.
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.
- The session
- The date
- The energy
- Posted to the record
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.
The order, on the services chassis.
Quote, order, posted.
The order transacts through the services.vin counter: one VIN, one order, one invoice.
- 01Quote
Live 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
- 02Order
Opens 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
- 03Posted
Posts 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
02Order
Not 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.
Order id, timestamps and amounts render live at the address. Structure, not prices.
Questions with posted answers.
The written quote is free. No account.
Can I order an install today?
Not yet. Installer papering and per-state kWh-metering and resale rules are in progress; the order action posts on this record the day they clear. The written quote is live today: free, no account.
Is the quote the final price?
When ordering opens, the posted quote is the order price. A site finding (the panel, the run) posts as a written revision you authorize before the work continues, never a number at the end.
Why does the charging line matter?
An electric car’s service history is its sessions. Posted with dates and energy, the line is a fact the next buyer can read, beside the decode and the battery fact in the Data layer.
How does charge.vin make money?
Our margin, posted per order as its own line beside the vendor cost. No fee appears at settlement that wasn’t on the quote.
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.
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.
The other addresses read the same seventeen characters. The free faces lead; the paid order is the deepening step.
- connects.vinYour charging network account: sessions posted with dates and energy
- sticker.vinWhat the car takes, as built: battery and range on the posted sticker
- data.vinThe battery is a record fact: it reads in the Data layer, beside the decode
- services.vinThe transacting counter: every job on the car, one order, one invoice
- values.vinThe charging history against the number: five values, posted
If an agent orders the charging for you, it reads this same record: the written quote, the posted sessions and the completion on the record are 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.
- Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the callb2a2cAn agent acting for a consumer: everything it does survives being shown to them afterward
- 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.