LogisticsOS API Services

Name: LogisticsOS API Services API
Brand: LogisticsOS API Services
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationRouting DirectionsapiKey12 EndpointsREST

For Agents

Solve vehicle routing and TSP problems, replan live routes, match GPS traces to roads, and calculate route matrices for fleet operations.

Install Jentic One Beta

Connect the LogisticsOS API Services to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LogisticsOS API Services, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 LogisticsOS API Services API.

Submit a Vehicle Routing Problem with vehicles, depots, and stops via POST /vrp/v3 and retrieve the optimised plan asynchronously

Solve a Traveling Salesman Problem for a single vehicle with POST /tsp/v3

Replan an in-progress route after disruptions through POST /replan/v3

GET STARTED

Start building with LogisticsOS API Services API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use LogisticsOS API Services API for, with concrete tasks.

★ Daily Delivery Route Optimisation

Generate the optimal delivery plan each morning by POSTing a Vehicle Routing Problem with the day's stops, vehicle constraints, and time windows to /vrp/v3. The solver returns a job id; poll GET /vrp/v3 with that id to retrieve sequenced routes per vehicle. This typically replaces manual dispatcher work for fleets above ~20 vehicles.

POST /vrp/v3 with the vehicles array and stops array, then GET /vrp/v3?id=<jobId> until status='complete'.

Live Replanning after Disruption

When a vehicle breaks down or a stop is cancelled, recompute the remaining plan with POST /replan/v3 using the current vehicle positions and the updated stop list. The replan engine reuses progress already made instead of solving from scratch, keeping ETAs accurate.

POST /replan/v3 with currentPositions and remainingStops, then poll GET /replan/v3?id=<jobId>.

Travel-Time Matrix for Distance Calculations

Build a pairwise travel-time matrix for a set of locations via POST /matrix/v1. The matrix powers downstream optimisation, ETA prediction, and what-if analysis without paying the full cost of solving a VRP each time.

POST /matrix/v1 with coordinates=[[lon1,lat1],[lon2,lat2],...] then GET /matrix/v1?id=<jobId>.

GPS Trace Map Matching

Snap noisy GPS traces from telematics devices to the actual road network using POST /match/v1. The cleaned trace produces accurate distance and street-name reporting and feeds proof-of-delivery and audit workflows.

POST /match/v1 with the raw trace coordinates and radius parameter to receive the matched route geometry.

AI Agent Route Planning via Jentic

An AI dispatcher agent can submit a VRP, poll the result, and dispatch the assigned routes to drivers without managing API keys. Jentic exposes the LogisticsOS solver and result endpoints as MCP tools so the agent invokes them by intent.

Through Jentic, search 'optimise vehicle routes', load the LogisticsOS POST /vrp/v3 operation, execute it, then load GET /vrp/v3 to fetch the result.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/vrp/v3

Submit a Vehicle Routing Problem

GET

/vrp/v3

Retrieve VRP result by job id

POST

/tsp/v3

Submit a Traveling Salesman Problem

POST

/replan/v3

Replan an in-progress route

POST

/ondemand/v3

Add stops to a live plan

POST

/route/v1

Calculate a route between coordinates

POST

/matrix/v1

Compute a travel-time matrix

POST

/match/v1

Snap a GPS trace to the road network

POST

/vrp/v3

Submit a Vehicle Routing Problem

GET

/vrp/v3

Retrieve VRP result by job id

POST

/tsp/v3

Submit a Traveling Salesman Problem

POST

/replan/v3

Replan an in-progress route

POST

/ondemand/v3

Add stops to a live plan

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The LogisticsOS API key is stored encrypted in the Jentic vault and injected at execution time. Agents call solver endpoints without ever seeing the raw key.

Intent-based discovery

Agents search by intent (e.g. 'optimise delivery routes') and Jentic returns the matching LogisticsOS operation with its input schema and response shape.

Time to first call

Direct LogisticsOS integration: 2-4 days to wire up auth, payload construction, async polling, and error handling. Through Jentic: under an hour.

FAQs

Specific to using LogisticsOS API Services API through Jentic.

Why is there no official OpenAPI spec for LogisticsOS API Services?

LogisticsOS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LogisticsOS API Services via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LogisticsOS API use?

LogisticsOS uses an API key passed in the request (ApiKeyAuth scheme). Through Jentic the key is held in the encrypted vault and injected at execution, so the raw key never appears in the agent's context.

How does the asynchronous VRP solver work?

Submit the problem with POST /vrp/v3 and the API returns a job id immediately. Poll GET /vrp/v3 with that id until status reports completion, then read the optimised routes from the response. The same pattern applies to /tsp/v3, /ondemand/v3, /replan/v3, and /matrix/v1.

Can I replan a route after a vehicle breaks down?

Yes. POST /replan/v3 with the current vehicle positions and the remaining stops, then poll GET /replan/v3 for the updated plan. The replanner reuses completed work instead of solving from scratch.

How do I optimise delivery routes through Jentic?

Run `pip install jentic`, search Jentic for 'optimise vehicle routes', load the LogisticsOS POST /vrp/v3 operation, and execute it with the vehicles and stops payload. Then load GET /vrp/v3 to fetch the result by job id.

What are the rate limits for the LogisticsOS API?

The spec does not embed numeric rate limits. Solver-style endpoints are job-throttled rather than request-throttled, so concurrent jobs are the relevant cap. Implement backoff on HTTP 429.

LogisticsOS API Services

Connect the LogisticsOS API Services to your agent

Capabilities

Start building with LogisticsOS API Services API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs