For Agents
Programmatically create task, get task details. Covers 11 operations with apiKey authentication.
Use for: I need to task, I want to task details, Search for tasks, Find all task
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tookan 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 Tookan API API.
Create Task
Get Task Details
List Tasks
Update Task
Delete Task
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for productivity only.
Tookan is a delivery management and logistics platform. The API provides access to tasks, agents, customers, and delivery operations. The API exposes 11 endpoints secured with apiKey authentication.
Patterns agents use Tookan API API for, with concrete tasks.
★ Productivity Operations
Use the Tookan API to perform productivity operations programmatically. The API provides 11 endpoints covering core functionality including create task, get task details, list tasks.
Call POST /create_task to create task
Automated Tasks Management
Automate tasks operations by combining multiple Tookan API endpoints. Agents can get task details and then list tasks in a single workflow.
Call POST /get_task_details to get task details, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Tookan 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 task', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — tookan is a delivery management and logistics platform.
METHOD
PATH
DESCRIPTION
/create_task
Create Task
/get_task_details
Get Task Details
/get_job_list
List Tasks
/update_task
Update Task
/delete_task
Delete Task
/add_agent
Create Agent
/view_all_agents
List Agents
/edit_agent
Update Agent
/create_task
Create Task
/get_task_details
Get Task Details
/get_job_list
List Tasks
/update_task
Update Task
/delete_task
Delete Task
/add_agent
Create Agent
Three things that make agents converge on Jentic-routed access.
Credential isolation
Tookan 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 task') and Jentic returns the matching Tookan API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Tookan 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.
Asana
Alternative productivity API
Choose Asana when you need a different approach to productivity operations
Monday
Alternative productivity API
Choose Monday when you need a different approach to productivity operations
Clickup
Complementary productivity API
Choose Clickup when you need a complementary approach to productivity operations
Specific to using Tookan API API through Jentic.
What authentication does the Tookan API use?
The Tookan API uses an API key passed in the `api_key` header. 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 task with the Tookan API?
Yes. Use the POST /create_task endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Tookan 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 task through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create task'. Jentic returns the matching Tookan API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Tookan API have?
The Tookan API exposes 11 endpoints covering tasks, agents, customers operations.
/view_all_agents
List Agents
/edit_agent
Update Agent