> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nozlerouting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nozle Routing API: fuel-optimal route planning

> Overview of the Nozle Routing API for fleet fuel-cost optimization, including the data model, three-endpoint pipeline, and how to start integrating.

Nozle is compute-only. We don't maintain a station database or pricing feed — partners bring their own station data, and we do the routing math.

## Data Model

**You provide:** stations with current prices, a vehicle, and trip endpoints (or a precomputed route).

**We provide:** route geometry, distance enrichment for your stations, the optimization algorithm, and a baseline comparison showing what naive refueling would cost.

This separation matters because (a) you almost certainly have more accurate price data than any third-party feed could provide, and (b) it keeps the API stateless — no syncing, no staleness, no licensing constraints on station coverage.

## Pipeline

Most partners use the three endpoints in sequence:

<Steps>
  <Step title="POST /v1/routes">
    Compute a driving route between two addresses.
  </Step>

  <Step title="POST /v1/stations/enrich-distances">
    Annotate your stations with route-relative positions and detour times.
  </Step>

  <Step title="POST /v1/optimize">
    Compute the optimal fueling plan, with savings vs. naive baseline.
  </Step>
</Steps>

Partners with their own routing can skip step 1 and pass a route directly into steps 2 and 3.

## Next Steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Complete integration example in Python, JavaScript, and cURL
  </Card>

  <Card title="Try the Demo" icon="play" href="https://demo.nozlerouting.com">
    Interactive walkthrough of the three-endpoint pipeline
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    API keys and request authentication
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Detailed endpoint documentation
  </Card>
</CardGroup>