One Fleet Technologies Ltd
The vehicle–
mission
decision API.
One Fleet is a decision API for commercial fleets. It combines vehicle specifications, payload, route, weather and operating conditions to assess whether a vehicle can reliably complete a working mission — before it is bought, allocated or dispatched.
It works for any fuel type. Payload, dimensions, working hours and clean air zone compliance are assessed for every vehicle; energy, range and charging are additional factors assessed when the vehicle is electric.
Marketplace platforms: filter jobs by vehicle fitInput
Vehicle
Model, usable battery capacity, official range, payload capacity, charge rate.
Payload
Mass at departure and how it changes across the working day.
Route
Distance, stop count, road mix, dwell time.
Conditions
Season or temperature, climate use, traffic allowance.
Charging
Depot, destination and public charging availability, minutes permitted.
Starting charge
State of charge at departure and required operating reserve.
Output
Decision
Suitable, suitable with conditions, further evidence required, or unsuitable.
Predicted arrival charge
State of charge on completion, against the required reserve.
Operational risks
The single risk most likely to end the mission early.
Required change
Charging stops and minutes, or the vehicle change that would resolve it.
Confidence
Designed to rise as comparable observed missions accumulate.
The learning loop
Predicted mission → real outcome → improved future assessment.
Every assessment can be validated against what actually happened: energy used, charge on completion, distance and charging stops. The difference between predicted and observed is the asset. It is what makes the next assessment for a comparable vehicle, payload and season better than the manufacturer figure.
Interface shape · planned
POST /v1/mission-assessment
{
"vehicle": {
"usable_battery_kwh": 58,
"stated_range_miles": 160,
"payload_capacity_kg": 950
},
"mission": {
"distance_miles": 120,
"stops": 14,
"payload_departure_kg": 600,
"temperature_c": 3,
"start_charge_percent": 100,
"required_reserve_percent": 15,
"depot_charging": "reliable"
}
}
200 OK
{
"decision": "suitable_with_conditions",
"arrival_charge_percent": 18,
"energy_required_kwh": 49.6,
"charging_stops": 0,
"principal_risk": "Cold-weather consumption leaves little margin above reserve.",
"confidence": "developing"
}Prototype. The calculation layer is live in this application; the public HTTP interface is a planned integration, not a released endpoint.
Who would call it
- Fleet operators assessing vehicles before purchase or lease.
- Allocation and dispatch systems choosing a vehicle for a round.
- Leasing providers and vehicle marketplaces qualifying suitability.
- Telematics, charge-point and manufacturer platforms adding a decision layer.
Expansion route, not current customers.