For Agents
Create, list, and update prioritized tasks with due dates and status tracking. Supports four priority levels and three workflow statuses for lightweight task management.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Prioritio 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 Prioritio API.
Create tasks with title, description, priority level, and due date
Filter task lists by status to focus on open or in-progress items
Update task priority from low through critical as urgency changes
GET STARTED
Use for: I need to create a high-priority task with a deadline, List all tasks that are currently in progress, I want to update the priority of task 42 to critical, Get the details of a specific task by its ID
Not supported: Does not handle project hierarchies, team collaboration, time tracking, or file attachments — use for priority-based task creation and status tracking only.
Jentic publishes the only available OpenAPI specification for Prioritio API, keeping it validated and agent-ready. Prioritio API provides task and priority management with 5 endpoints for creating, listing, retrieving, and updating tasks. Each task supports four priority levels (low, medium, high, critical) and three status stages (open, in_progress, completed), with due dates for deadline tracking. The API also exposes priority configuration data for customizing how tasks are categorized.
Transition tasks through open, in_progress, and completed statuses
Retrieve priority configurations including level names and color codes
Patterns agents use Prioritio API for, with concrete tasks.
★ Priority-Based Task Triage
Use the Prioritio API to triage incoming work items by assigning priority levels from low to critical. Agents can list all open tasks filtered by status, identify items lacking a priority assignment, and batch-update priorities based on due date proximity or business rules. This is particularly useful for teams processing inbound requests where items need rapid categorization.
List all tasks with status 'open', identify any without a priority set, and update them to 'medium' priority
Deadline Tracking and Status Updates
Track task deadlines and transition items through workflow stages as work progresses. The API stores due_date on each task and supports status values of open, in_progress, and completed. Agents can identify overdue tasks by comparing due_date against the current date and move completed work to the done state without manual intervention.
Retrieve all tasks with status 'in_progress', check which have a due_date before today, and update those overdue tasks to include 'OVERDUE' in their description
AI Agent Task Management Integration
AI agents can use the Prioritio API through Jentic to manage task backlogs, create items from parsed emails or messages, and keep priority assignments aligned with business goals. Jentic provides the structured operation schemas and credential isolation so agents can call Prioritio endpoints without storing bearer tokens in their context.
Search Jentic for 'create a prioritized task', load the createTask operation schema, and execute it with title 'Review Q3 report', priority 'high', and due_date '2026-07-01'
5 endpoints — jentic publishes the only available openapi specification for prioritio api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/tasks
List tasks with status and pagination filters
/tasks
Create a new task with priority and due date
/tasks/{id}
Retrieve a specific task by ID
/tasks/{id}
Update task priority, status, or details
/priorities
List priority level configurations
/tasks
List tasks with status and pagination filters
/tasks
Create a new task with priority and due date
/tasks/{id}
Retrieve a specific task by ID
/tasks/{id}
Update task priority, status, or details
/priorities
List priority level configurations
Three things that make agents converge on Jentic-routed access.
Credential isolation
Prioritio bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped session credentials and never see the raw API token in their context window.
Intent-based discovery
Agents search by intent (e.g., 'create a high-priority task' or 'list overdue tasks') and Jentic returns matching Prioritio operations with input schemas, so the agent constructs the correct request without reading docs.
Time to first call
Direct Prioritio integration: half a day for auth and endpoint mapping. Through Jentic: under 30 minutes using pip install jentic, search, load, and execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Prioritio API through Jentic.
Why is there no official OpenAPI spec for Prioritio API?
Prioritio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Prioritio API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Prioritio API use?
The Prioritio API uses Bearer token authentication. Include your token in the Authorization header as 'Bearer your-token'. Through Jentic, the bearer token is stored encrypted in the credential vault and agents receive scoped access without handling raw credentials.
What priority levels does the Prioritio API support?
The API supports four priority levels: low, medium, high, and critical. These are defined as an enum on the task priority field and also available through the GET /priorities endpoint which returns configuration details including level names and associated color codes.
Can I filter tasks by status with the Prioritio API?
Yes. The GET /tasks endpoint accepts a status query parameter with values 'open', 'in_progress', or 'completed'. This allows you to retrieve only tasks in a specific workflow stage without client-side filtering. The endpoint also supports page and limit parameters for pagination.
How do I create a task with a deadline through Jentic?
Search Jentic for 'create a prioritized task', load the createTask operation schema, and execute with a JSON body containing title (required), plus optional description, priority (low/medium/high/critical), and due_date in YYYY-MM-DD format. Install with pip install jentic and set your JENTIC_AGENT_API_KEY environment variable.
What are the rate limits for the Prioritio API?
The Prioritio API specification does not document explicit rate limits. Standard API best practices apply. If you encounter throttling responses, implement exponential backoff in your retry logic.