Fuel-Optimal Route Planning
for Fleet Operators

Nozle computes provably near-optimal fuel stops across complete routes using live station prices. Built for fleet management software, fleet card companies, and TMS platforms that need real savings — not estimates.

30–40%
of fleet OPEX is fuel
Sub 1 Second
latency typical for optimization
6–11%
typical fuel savings

Fuel is 30–40% of fleet operating cost.
Most routing tools ignore it.

Existing routing tools optimize for time and distance. They don't model fuel price, tank capacity, or the cost of detour — the variables that actually cost you money.

Refueling at the first available station

Drivers stop where it's convenient, not where it's cheapest. A $0.40/gal swing across a 200-mile corridor can cost $30+ per fill-up on a 75-gal tank.

Routing tools optimize distance, not fuel cost

Shortest-path routing ignores price variance entirely. A short five minute detour can save companies hundreds of dollars a year.

Fuel cards show prices, but not where to stop

Card programs surface station prices, but the driver still has to do the math — and they don't, especially on multi-stop routes with tank constraints.

Provably Near-Optimal Routing
across complete routes.

Nozle takes your origin, destination, vehicle parameters, and a set of candidate stations with live prices. It returns the fuel stops and quantities that minimize total cost subject to tank, time, and detour constraints.

  • Whole-route optimization. We solve over the entire trip, not segment by segment.
  • Tank-aware. Capacity, reserve, and refuel-time constraints are part of the model, not an afterthought.
  • Provable guarantees. Every result includes a baseline comparison showing what naive refueling would have cost — so you can quantify the savings on every trip.
Example scenarioLA → Chicago · 2,017 mi
Naive (first station)
$1192
7 stops · 240 gal tank
Nozle optimal
$1048
3 stops · 240 gal tank
Savings on this run
$144 · 12.1%
Across a 200-truck fleet
~$28,800 / week

Three patterns.
Same API.

Nozle is a routing primitive — you decide where it sits in your stack. Most customers start with one pattern and add others as their product evolves.

Plan-time integration

Call Nozle when a route is created. Get a fully optimized fuel plan back in under a second. Drop into existing dispatch flows.

Your TMS
Nozle API
Optimal stops

In-cab guidance

Embed in driver-facing apps. Compute optimal stops mid-route as prices change or constraints shift. Re-optimize on demand.

Driver app
Nozle API
Updated plan

Card-network steering

Fleet card programs surface recommended stations to drivers based on full-route optimization, not just nearby prices.

Card program
Nozle API
Steered stops

You provide stations and prices.
We provide the algorithm.

Nozle doesn't store your station data, broker price feeds, or compete with your data providers. You bring the inputs you already license; we return the optimal plan.

  • No licensing conflicts. Use whatever station feed you already pay for — OPIS, GasBuddy, or your fleet card's network.
  • Data sent as received. Pass-through metadata. Extra fields you attach to stations or routes are returned unchanged, so you can preserve your internal identifiers and metadata
  • No PII. Routes are processed in-memory and not retained beyond the request.
data flow
Route
origin, destination, waypoints
Vehicle
tank, MPG, reserve
Stations
ID, lat/lng, price, brand
NOZLE ENGINE
≤400ms · stateless
Optimal Plan
stops[] · quantities[] · total_cost · expected savings
60 seconds

See it working.
Without an account.

Try a live route with synthetic station data and see the optimal stops, prices, and savings — instantly.

Launch the Demo →

One endpoint.
Clean JSON.

REST, JSON, no SDK required. Bring your station list and route; get back an optimal plan with a suboptimality bound.

POST /v1/optimize
import requests

result = requests.post('https://api.nozlerouting.com/v1/optimize',
    headers={'X-API-Key': 'YOUR_API_KEY'},
    json={
        'route': {
            'total_distance_miles': 1287.4,
            'total_duration_minutes': 1124.8,
            'start': {'lat': 32.7767, 'lng': -96.7970},
            'end':   {'lat': 33.7490, 'lng': -84.3880},
        },
        'stations': [
            {
                'id': 'WEX_45821',
                'name': 'Pilot Travel Center #234',
                'location': {'lat': 32.9, 'lng': -94.1},
                'price_per_gallon': 4.12,
                'fuel_type': 'diesel',
                'miles_from_route_start': 187.3,
                'detour_minutes': 2.1,
            },
            # ... more stations
        ],
        'vehicle': {
            'mpg': 6.5,
            'tank_capacity_gallons': 240.0,
            'current_fuel_gallons': 40.0,
        },
    },
).json()

print(f"Optimal stops: {len(result['stops'])}")
print(f"Savings: ${result['summary']['baseline_comparison']['savings_dollars']:.2f}")

API at a glance

  • P50 latency~120ms
  • P95 latency≤400ms
  • Rate limit60-120 req/min
  • AuthIntegration Token Provided Per Client
  • SDKsREST/JSON — integrate from any language
Full API Docs →

Built for the platforms
that move fleets.

For

Fleet management software

Add fuel-aware routing to your platform without building an optimization team. Customers see immediate savings on the routes you already plan.

For

Fleet card companies

Steer drivers to stations on your network where you have the best margin while still delivering optimal cost. Differentiate beyond rebates.

For

TMS & logistics platforms

Layer fuel optimization onto existing route-planning workflows. One API call, one drop-in line item in your savings dashboard.

Request access
or just say hi.

We're working with a small number of early partners. If you're building fleet software, run a card program, or operate a TMS, drop a note and we'll get back within a day.