Developer platform

Fuel optimization as a background service.

Push vehicle locations to the API and get back the cheapest on-route diesel stop for every truck — continuously. FuelAtlas handles the routing, live prices, your discounts, and IFTA. You integrate in an afternoon.

Start building API reference

No login to read the docs Sandbox on every key REST · Webhooks · MCP

fuelatlas — guidance

$ curl https://api.fuelatlas.com/v1/vehicles/veh_5tR/guidance \
  -H "Authorization: Bearer fa_test_…"

{
  "phase": "stop_recommended",
  "data_freshness": "fresh",
  "stops": [{
    "station": { "name": "TA Bucksville", "chain": "TA Petro" },
    "distance_ahead_miles": 128.4,
    "gallons_to_buy": 140,
    "price_usd_per_gallon": 3.499,
    "discount_usd_per_gallon": 0.42,
    "savings_vs_baseline_usd": 58.80,
    "reason": "Cheapest net stop within range."
  }]
}

Pick your path

Three ways in

TMS

TMS vendors

Provision fleets, sync vehicles, and surface the right fuel stop inside your dispatch UI — for every customer you manage.

TMS quickstart ELD

ELD vendors

You already stream GPS and tank level. Pipe it in and push fuel-low and guidance events straight into the driver's cab.

ELD quickstart AI

AI-agent builders

Give an agent fuel context via llms.txt and the MCP server, or call a one-shot optimize. Every rationale is human-readable.

AI-agents quickstart

Your first request

Read a recommendation in one call.

Every endpoint is REST + JSON over HTTPS. Authenticate with a Bearer key, call the guidance endpoint for a vehicle, and read stops[0] — the station, how many gallons to buy, the net price, and a reason you can show a driver verbatim.

Use a fa_test_ key and it runs against the simulated sandbox fleet — no real truck required.

Get a key → Authentication

curl https://api.fuelatlas.com/v1/vehicles/veh_5tR/guidance \
  -H "Authorization: Bearer fa_test_your_key"

import requests

r = requests.get(
    "https://api.fuelatlas.com/v1/vehicles/veh_5tR/guidance",
    headers={"Authorization": "Bearer fa_test_your_key"},
)
print(r.json()["stops"][0]["station"]["name"])

const res = await fetch(
  "https://api.fuelatlas.com/v1/vehicles/veh_5tR/guidance",
  { headers: { Authorization: "Bearer fa_test_your_key" } },
);
const guidance = await res.json();
console.log(guidance.stops[0].station.name);

using var http = new HttpClient();
http.DefaultRequestHeaders.Authorization = new("Bearer", "fa_test_your_key");
var g = await http.GetFromJsonAsync<JsonElement>(
    "https://api.fuelatlas.com/v1/vehicles/veh_5tR/guidance");
Console.WriteLine(g.GetProperty("stops")[0].GetProperty("station").GetProperty("name"));

One key, clear scopes

Bearer API keys with OAuth-style scopes. Partner keys manage many fleets via one header. GET /v1/me tells an integration exactly what it can do.

Continuous autoguide

Bind a vehicle to a destination; read the cheapest on-route stop as it drives — costed, with a driver-ready reason and a data-freshness grade.

Signed webhooks

Thirteen event types, HMAC-SHA256 signatures, retries, replay, and dual-valid secret rotation. Stop polling.

A real sandbox

fa_test_ keys drive a simulated fleet with synthetic prices and scenarios. Build and run CI without a live truck.