Install Jentic One Beta

Connect the RouteLogic API to your agent

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" | 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%2Froutelogic.io%2Froutelogic" | 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 RouteLogic API.

Create or update tasks

Get paginated collection of tasks

Update task

Partially update task

Delete task

Use Cases

GET STARTED

Start building with RouteLogic API

Explore with Jentic One

View OpenAPI Document

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

Key Endpoints

10 endpoints — routelogic api for managing tasks, visits, and logistics operations.

METHOD

PATH

DESCRIPTION

POST

/api/v2/tasks

Create or update tasks

GET

/api/v2/tasks

Get paginated collection of tasks

GET

/api/v2/tasks/{task_uuid}

Get single task

PUT

/api/v2/tasks/{task_uuid}

Update task

PATCH

/api/v2/tasks/{task_uuid}

Partially update task

DELETE

/api/v2/tasks/{task_uuid}

Delete task

POST

/api/v2/tasks/{task_uuid}/products

Create task product

GET

/api/v2/tasks/{task_uuid}/products

Get task products

POST

/api/v2/tasks

Create or update tasks

GET

/api/v2/tasks

Get paginated collection of tasks

GET

/api/v2/tasks/{task_uuid}

Get single task

PUT

/api/v2/tasks/{task_uuid}

Update task

PATCH

/api/v2/tasks/{task_uuid}

Partially update task

DELETE

/api/v2/tasks/{task_uuid}

Delete task

POST

/api/v2/tasks/{task_uuid}/products

Create task product

GET

/api/v2/tasks/{task_uuid}/products

Get task products

Why Jentic?

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.

FAQs

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.

RouteLogic API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityTask Managementbearer10 EndpointsREST

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RouteLogic API to your agent

Capabilities

Use Cases

Start building with RouteLogic API

Key Endpoints

Why Jentic?

Related APIs

FAQs

RouteLogic API

Jentic AI Readiness Score

RouteLogic API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness