Charging Value · inside the mission workflow
The cheapest tariff is rarely the cheapest charge.
Which charger offers the lowest total cost that will actually work for this vehicle, driver and mission? Not a discount directory, not a charging wallet, not a route planner.
Cheapest to pay
The lowest charging payment on the receipt.
Cheapest overall
Payment plus detour energy, parking, waiting and driver time.
Most dependable
The suitable option with the strongest recent evidence.
Run Charging Value
Enter or confirm the vehicle, the mission and your driver economics. Suitability is decided on physical reality, not on connector compatibility alone.
Vehicle, mission and driver economics
Your entriesMemberships or subscriptions held
Calculated live from your entries against fictional reference locations. No live tariff feed, availability feed or real operator is used.
Where each value comes from
Operator-supplied
Tariffs, session fees, power ratings and stated conditions as published by the site owner.
Public regulatory data
Parking orders, access charges and restrictions from public records.
Driver observation
What a named driver actually observed, with the date it was observed.
Inferred by Deliverd
Values Deliverd derived — always labelled, never presented as observed fact.
A charger is never described as dependable on the strength of one successful session, and insufficient evidence is never converted into a positive recommendation.
Zero tariff is not zero cost
- A read-only internal feed of locations that may qualify as free charging.
- A zero electricity tariff never means a zero-cost mission: parking, required purchase, detour energy, waiting and driver time are always calculated.
- Free-charging eligibility conditions expire and are re-checked, not assumed.
- No discount, voucher or free session is ever invented to make an option look better.
Private fleet pilot
Pilot reporting
No results yetPilot operators see their own measured record only. Nothing here is populated with invented performance, savings or customer names.
- Missions assessedAwaiting pilot data
- Charging recommendations issuedAwaiting pilot data
- Predicted versus actual costAwaiting pilot data
- Avoided failed visitsAwaiting pilot data
- Avoided delayAwaiting pilot data
- Data gaps discoveredAwaiting pilot data
- Estimated savingsAwaiting pilot data
- Evidence coverageAwaiting pilot data
Data management, endpoints and scope+−
Every material change keeps its version history and timestamp. Corrections create new versions; they do not quietly overwrite what was recorded before.
Data objects: Charger records, Tariffs, Subscriptions, Discounts and expiry, Vehicle compatibility, Physical-site evidence, Driver observations, Receipt review, Disputed records, Operator corrections, Data-source health, Duplicate locations. Charger records — Location identity, power, connectors, public access, hours. Tariffs — Rate per kWh, session fees, effective dates, who supplied them. Subscriptions — Scheme, allocation, eligibility conditions. Discounts and expiry — Discount value, start and expiry date, eligibility test. Vehicle compatibility — Connector, maximum rate, dimensional limits per vehicle class. Physical-site evidence — Bay dimensions, barriers, restrictions, obstruction, lighting. Driver observations — Queue, damage, facilities, successful commercial visits. Receipt review — Extracted values held as suggestions until a human confirms them. Disputed records — Two conflicting accounts retained side by side, neither overwritten. Operator corrections — Operator-supplied change recorded as a new version, not an edit. Data-source health — Feed freshness, failure rate, last successful refresh. Duplicate locations — Candidate duplicates queued for human merge.
Authenticated endpoint shapes, shared with development-access partners: POST /api/v1/charging-value/check (Accepts a vehicle and mission profile. Returns ranked options with cost components, suitability verdict, confidence and stated limitations.); GET /api/v1/charging-value/location/{id} (Returns the location record with evidence fields, sources and evidence age.); POST /api/v1/charging-value/outcome (Records the observed outcome of a charging stop beside the original prediction.); POST /api/v1/charging-value/evidence (Submits a physical-site observation with its source and observation date.); POST /api/v1/charging-value/challenge (Challenges a record or a cost component; the challenge is retained with the disputed value.). Personal driver data and private receipts are never exposed through the public API.
Deliberately out of scope: Payment processing, Charging-network roaming, A stored payment wallet, Automatic charger reservations, Fabricated live availability, Another consumer application, Autonomous dispatch without human approval.