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.

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

Yes. Because you run Jentic One yourself, your own rules decide which LogisticsOS operations and credentials the agent may use. Since every solver call carries its whole problem in the request body with no account resource in the URL, scoping is by operation: you can allow only the endpoints the agent needs, such as POST /vrp/v3 for vehicle routing or POST /matrix/v1 for travel-time matrices. Operations the agent does not need, like POST /ondemand/v3 for live stops or POST /match/v1 for GPS map matching, can be left out so it never calls them.