NetworkFleet API

Name: NetworkFleet API
Brand: NetworkFleet API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey3 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the NetworkFleet API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetworkFleet API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetworkfleet.com%2Fnetworkfleet" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetworkfleet.com%2Fnetworkfleet" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NetworkFleet API.

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

GET STARTED

Start building with NetworkFleet API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NetworkFleet API for, with concrete tasks.

★ 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.

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.

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.

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

3 endpoints — jentic publishes the only available openapi specification for networkfleet api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/vehicles

List vehicles

GET

/vehicles/{vehicleId}/location

Get a vehicle's last reported location

GET

/trips

List trip history

GET

/vehicles

List vehicles

GET

/vehicles/{vehicleId}/location

Get a vehicle's last reported location

GET

/trips

List trip history

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using NetworkFleet API through Jentic.

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.