For Agents
Programmatically create a new optimization, retrieve optimization(s). Covers 5 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Route4Me Route Optimization 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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 instanceJentic 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.
What an agent can do with Route4Me Route Optimization API.
Create a new optimization
Retrieve optimization(s)
Update an optimization
Delete an optimization
GET STARTED
Use for: I need to a new optimization, I want to optimization(s), Search for an optimization, Find all an optimization
Not supported: Does not handle payments, communications, or crm — use for analytics only.
Cloud-based route optimization API for logistics and fleet management. Provides route planning, optimization, and tracking capabilities. The API exposes 5 endpoints secured with apiKey authentication.
Get activity feed
Patterns agents use Route4Me Route Optimization API for, with concrete tasks.
★ Analytics Operations
Use the Route4Me Route Optimization API to perform analytics operations programmatically. The API provides 5 endpoints covering core functionality including create a new optimization, retrieve optimization(s), update an optimization.
Call POST /api.v4/optimization_problem.php to create a new optimization
Automated Optimizations Management
Automate optimizations operations by combining multiple Route4Me Route Optimization API endpoints. Agents can retrieve optimization(s) and then update an optimization in a single workflow.
Call GET /api.v4/optimization_problem.php to retrieve optimization(s), then verify the result
AI Agent Integration via Jentic
AI agents discover and call Route4Me Route Optimization API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create a new optimization', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — cloud-based route optimization api for logistics and fleet management.
METHOD
PATH
DESCRIPTION
/api.v4/optimization_problem.php
Create a new optimization
/api.v4/optimization_problem.php
Retrieve optimization(s)
/api.v4/optimization_problem.php
Update an optimization
/api.v4/optimization_problem.php
Delete an optimization
/api/get_activities.php
Get activity feed
/api.v4/optimization_problem.php
Create a new optimization
/api.v4/optimization_problem.php
Retrieve optimization(s)
/api.v4/optimization_problem.php
Update an optimization
/api.v4/optimization_problem.php
Delete an optimization
/api/get_activities.php
Get activity feed
Three things that make agents converge on Jentic-routed access.
Credential isolation
Route4Me Route Optimization API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a new optimization') and Jentic returns the matching Route4Me Route Optimization API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Route4Me Route Optimization API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Route4Me Route Optimization API through Jentic.
What authentication does the Route4Me Route Optimization API use?
The Route4Me Route Optimization API uses an API key passed in the `api_key` query. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create a new optimization with the Route4Me Route Optimization API?
Yes. Use the POST /api.v4/optimization_problem.php endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Route4Me Route Optimization API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new optimization through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new optimization'. Jentic returns the matching Route4Me Route Optimization API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Route4Me Route Optimization API have?
The Route4Me Route Optimization API exposes 5 endpoints covering optimizations, activities operations.