canonical: https://jentic.com/apis/networkfleet.com/networkfleet

# NetworkFleet API

Jentic publishes the only available OpenAPI specification for NetworkFleet API, keeping it validated and agent-ready. NetworkFleet is a fleet telematics platform - historically Verizon NetworkFleet - that tracks vehicle location, driver trips, and on-board diagnostics for commercial fleets. The API exposes vehicle inventory, current location, and trip history endpoints suitable for dispatch, route optimisation, and fleet utilisation reporting.

## For AI agents

List vehicles, fetch their current location, and read trip history from the NetworkFleet telematics platform.

## Scope

Does not handle driver behaviour scoring, dashcam video, or fuel and engine diagnostics - use for vehicle inventory, location, and trip history only.

## Capabilities

- List every vehicle currently provisioned on the fleet account
- Fetch a vehicle's last reported location with timestamp
- Retrieve historical trip records for a date range
- Power a dispatch board with live location pins
- Calculate vehicle utilisation and idle time from trip history

## Use cases

### Live Dispatch Board

Power a dispatch board that pins each vehicle's last reported position on a map and refreshes on a schedule. The vehicle list and per-vehicle location endpoints together give dispatchers a real-time view without opening the NetworkFleet portal.

Example prompt: List all vehicles via /vehicles and call `/vehicles/{vehicleId}/location` for each, returning a list of {vehicleId, lat, lng, timestamp}.

### Fleet Utilisation Reporting

Pull trip history for a reporting window and compute per-vehicle drive time, idle time, and total miles. Feed the result into a finance or operations report so leasing and maintenance decisions are grounded in actual usage rather than odometer snapshots.

Example prompt: Fetch /trips for the last 30 days, group by vehicleId, and return total drive minutes and total miles per vehicle.

### AI Agent Fleet Q&A

Let an AI agent answer 'where is truck V-123 right now?' or 'how many trips did V-7 make yesterday?' through Jentic. The agent calls the right NetworkFleet endpoint and replies in plain English, removing the need for non-technical users to log into the portal.

Example prompt: Given the question 'where is vehicle V-123?', call `/vehicles/V-123/location` and return the address resolved from the lat/lng plus the timestamp.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/vehicles` | List vehicles |
| GET | `/vehicles/{vehicleId}/location` | Get a vehicle's last reported location |
| GET | `/trips` | List trip history |

## Key resources

- **Vehicles** — Vehicles provisioned on the fleet account
- **Vehicle Location** — Last reported location for a vehicle
- **Trips** — Historical trip records

## Why Jentic

- **Setup:** Wiring the NetworkFleet API by hand means setting its Authorization API key header, targeting the api.networkfleet.com host, and shaping vehicle inventory, location, and trip-history calls yourself. Through Jentic you install once, import NetworkFleet from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** NetworkFleet puts the vehicle id in the URL path (`/vehicles/{vehicleId}/location`), so a rule can pin your agent to one vehicle. You choose the operations it may call, so the full trips listing is not included unless you add it.
- **Credential handling:** Your NetworkFleet API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'where is my fleet vehicle' or 'list recent trips', and Jentic returns the matching NetworkFleet operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Samsara API** — Samsara is a modern fleet telematics platform with a much broader API surface covering driver, video, and asset data.
- **Trimble FSM API** — Trimble Field Service Management offers fleet and crew dispatch on a separate telematics stack.
- **Telematics SDK API** — Telematics SDK provides cross-vendor abstraction over driver behaviour data that pairs with NetworkFleet trip records.

## FAQ

### Why is there no official OpenAPI spec for the NetworkFleet API?

NetworkFleet (Verizon Connect) does not publish a public OpenAPI specification for this surface. Jentic generates and maintains this spec so that AI agents and developers can call NetworkFleet API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the NetworkFleet API use?

NetworkFleet uses API key authentication issued per fleet account, passed in a request header. Through Jentic the key is stored encrypted in the vault and injected at request time, so it never appears in the agent's prompt context.

### Can I get a vehicle's current location with the NetworkFleet API?

Yes. GET `/vehicles/{vehicleId}/location` returns the last reported latitude, longitude, and timestamp for that vehicle. Combine with /vehicles to iterate over the whole fleet for a live dispatch view.

### What are the rate limits for the NetworkFleet API?

NetworkFleet does not publish a public per-second rate limit; throughput depends on the fleet plan. For high-frequency location polling, consider per-vehicle backoff and confirm peak limits with the NetworkFleet account team.

### How do I pull trip history through Jentic?

Run jentic.search('get fleet trip history'), load the matching operation, and execute GET /trips with a date range. Jentic returns the trip records that the agent can group by vehicle for utilisation reporting.

### Does the NetworkFleet API support driver behaviour or fuel data?

This OpenAPI surface focuses on vehicle inventory, location, and trip history. Driver behaviour scoring, fuel consumption, and engine diagnostics live in adjacent NetworkFleet products that require separate onboarding.

### Can I limit what my agent is allowed to do with the NetworkFleet API?

Yes. Jentic One runs self-hosted, so your own rules decide which NetworkFleet operations and credentials the agent may use. Because the vehicle id sits in the URL path for GET `/vehicles/{vehicleId}/location`, you can pin the agent to a single vehicle instead of the whole fleet. You also choose the operations it may call, so the full GET /trips history listing is excluded unless you explicitly allow it, and the GET /vehicles inventory call can be left out entirely.