Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RouteLogic 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%2Froutelogic.io%2Froutelogic" | shStep 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%2Froutelogic.io%2Froutelogic" | 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 RouteLogic API.
Create or update tasks
Get paginated collection of tasks
Update task
Partially update task
Delete task
GET STARTED
Patterns agents use RouteLogic API for, with concrete tasks.
★ Productivity Operations
Use the RouteLogic API to perform productivity operations programmatically. The API provides 10 endpoints covering core functionality including create or update tasks, get paginated collection of tasks, get single task.
Call POST /api/v2/tasks to create or update tasks
Automated Task Products Management
Automate task products operations by combining multiple RouteLogic API endpoints. Agents can get paginated collection of tasks and then get single task in a single workflow.
Call GET /api/v2/tasks to get paginated collection of tasks, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RouteLogic 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 bearer tokens manually.
Search Jentic for 'create or update tasks', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — routelogic api for managing tasks, visits, and logistics operations.
METHOD
PATH
DESCRIPTION
/api/v2/tasks
Create or update tasks
/api/v2/tasks
Get paginated collection of tasks
/api/v2/tasks/{task_uuid}
Get single task
/api/v2/tasks/{task_uuid}
Update task
/api/v2/tasks/{task_uuid}
Partially update task
/api/v2/tasks/{task_uuid}
Delete task
/api/v2/tasks/{task_uuid}/products
Create task product
/api/v2/tasks/{task_uuid}/products
Get task products
/api/v2/tasks
Create or update tasks
/api/v2/tasks
Get paginated collection of tasks
/api/v2/tasks/{task_uuid}
Get single task
/api/v2/tasks/{task_uuid}
Update task
/api/v2/tasks/{task_uuid}
Partially update task
/api/v2/tasks/{task_uuid}
Delete task
/api/v2/tasks/{task_uuid}/products
Create task product
/api/v2/tasks/{task_uuid}/products
Get task products
What agents get from Jentic-routed access to this vendor.
Setup
Wiring RouteLogic by hand means setting up its bearer token auth against api.routelogic.io and writing your own retry and pagination handling for the task collection. Through Jentic you install once, import RouteLogic from the API Directory, store the token once, and your agent calls it.
Permission scoping
RouteLogic puts the task id in the URL path (/api/v2/tasks/{task_uuid}), so a rule can pin your agent to one task: it can read and update that task and nothing else. You choose the operations it may call, so destructive ones like task deletion are not included unless you add them.
Credential isolation
Your RouteLogic bearer token 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 'create a task' or 'list open tasks', and Jentic returns the matching RouteLogic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using RouteLogic API through Jentic.
What authentication does the RouteLogic API use?
The RouteLogic API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create or update tasks with the RouteLogic API?
Yes. Use the POST /api/v2/tasks endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RouteLogic 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 or update tasks through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create or update tasks'. Jentic returns the matching RouteLogic API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the RouteLogic API have?
The RouteLogic API exposes 10 endpoints covering task products, tasks, visits operations.
Can I limit what my agent is allowed to do with the RouteLogic API?
Yes. Because Jentic One is self-hosted, your own rules decide which RouteLogic operations and credentials the agent may use. Since the task id sits in the URL path (/api/v2/tasks/{task_uuid}), you can pin the agent to a single task so it only reads and updates that task and nothing else. You choose exactly which operations it may call, so destructive ones like DELETE /api/v2/tasks/{task_uuid} stay out of reach unless you explicitly add them.
For Agents
Programmatically create or update tasks, get paginated collection of tasks. Covers 10 operations with bearer authentication.
Use for: I need to or update tasks, I want to paginated collection of tasks, Search for single task, Find all task
Not supported: Does not handle payments, communications, or crm - use for productivity only.
RouteLogic API for managing tasks, visits, and logistics operations. The API exposes 10 endpoints secured with bearer authentication.