Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hourtick 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%2Fhourtick.com%2Fhourtick" | 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%2Fhourtick.com%2Fhourtick" | 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 Hourtick API.
Start, stop, and edit time entries through a single idempotent commands endpoint
Read time entries, reports, and timesheets for a period
Manage a task board with work items, comments, checklists, and dependencies
Create clients, projects, and task types in the workspace catalog
Generate invoices from billable time through the workspace's Stripe connection
GET STARTED
Link tasks to Linear, Notion, Teamwork, and Asana items
Track AI agent sessions, costs, and outcomes against budgets
Patterns agents use Hourtick API for, with concrete tasks.
★ AI Agent Time Logging
An AI agent connected through Jentic can log its own working time against a task without a human filling a timesheet. The agent searches for the commands operation, Hourtick returns its input schema, and the agent sends a start command with a fresh command id, then a stop command when the work is done. This keeps agent and human effort in one ledger.
Start a timer on a task with a fresh command id and stop it when the work is done
Task Board Automation
Create and update work items on the task board, add checklist items, post comments, and set dependencies so a task cannot move forward until its blockers are done. An automation can keep the board in sync with external events without manual clicking.
Create a task, add a checklist item, and post a comment on it
Time Reporting
Pull totals, groups, and entries for a period, scoped to a team for managers, with cost and profit figures for admins. This feeds dashboards and periodic summaries without exporting spreadsheets by hand.
Fetch the time report for a project over a date range
Invoicing from Billable Time
Preview what an invoice would contain, then create and send it from a client's billable, not-yet-invoiced time through the workspace's Stripe account. The invoiced time is locked so it is not billed twice.
Preview an invoice for a client's billable time, then create and send it
134 endpoints — the hourtick api runs time tracking, task management, and client invoicing for a workspace.
METHOD
PATH
DESCRIPTION
/api/v1/commands
Start, stop, or edit time
/api/v1/time-entries
Time entries in a date range
/api/v1/reports
Totals and groups for a period
/api/v1/work-items
Create a task
/api/v1/work-items
List tasks on the board
/api/v1/invoices
Create and send an invoice
/api/v1/bootstrap
Current user, workspace, and projects
/api/v1/work-items/{id}/comments
Comment on a task
/api/v1/commands
Start, stop, or edit time
/api/v1/time-entries
Time entries in a date range
/api/v1/reports
Totals and groups for a period
/api/v1/work-items
Create a task
/api/v1/work-items
List tasks on the board
/api/v1/invoices
Create and send an invoice
/api/v1/bootstrap
Current user, workspace, and projects
/api/v1/work-items/{id}/comments
Comment on a task
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Hourtick API by hand means setting up a personal Bearer token, routing every timer change through its commands endpoint with a fresh idempotency UUID, and handling RFC 9457 error details. Through Jentic you install once, import Hourtick from the API Directory, store the token once, and your agent calls it.
Permission scoping
Hourtick separates read endpoints (time entries, reports, tasks) from write and admin operations like invoicing, member cost rates, and deleting tasks or files, so a rule can hold your agent to logging time and reading reports. You choose the operations it may call, so creating an invoice or deleting a task is not included unless you add it.
Credential isolation
Your Hourtick 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 'start a timer on a task' or 'get my time report', and Jentic returns the matching Hourtick operation with its input schema so the agent calls the right endpoint without reading the docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Hourtick API through Jentic.
What authentication does the Hourtick API use?
The Hourtick API authenticates with a personal Bearer token per its OpenAPI spec: create one in your account settings and send it in the Authorization header. Agents can be issued their own token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.
Can I start and stop timers with the Hourtick API?
Yes. All timer changes, starting, stopping, continuing, creating, editing, deleting, and restoring time, go through a single commands endpoint that is idempotent per command id, so retrying with the same id is safe.
Is there a Hourtick MCP server?
You don't need an MCP server to give your agent the Hourtick API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the time, task, and report endpoints it needs.
Can I limit what my agent is allowed to do with the Hourtick API?
Yes. Write a rule that allows only the time-logging commands and the read endpoints, so a tracking agent can record and report time while invoicing, cost-rate changes, and deletions stay out of reach, and every call it makes is logged.
What are the rate limits for the Hourtick API?
The OpenAPI spec does not publish specific rate limits. Every response carries a Server-Time header you can use for client-side pacing. Check hourtick.com for any limits that apply to your plan.
How do I log time with the Hourtick API through Jentic?
Search Jentic for an intent like 'start a timer on a task', and it returns the Hourtick commands operation with its input schema so your agent calls it with a command id and a task. Your stored token is injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Track time, manage a task board, and invoice billable work for a workspace. Agents can start and stop timers, create tasks, pull reports, and link work to Linear, Notion, Teamwork, and Asana.
Use for: Start a timer on a task, Stop the running time entry, Get my time entries for this week, Create a task on the board
Not supported: Does not run payroll, manage HR records, or host video calls. Use for time tracking, task management, and client invoicing only.
The Hourtick API runs time tracking, task management, and client invoicing for a workspace. All timer changes flow through a single idempotent commands endpoint, while separate endpoints read time entries, reports, and timesheets. It manages a task board of work items with comments, checklists, and dependencies, keeps a catalog of clients, projects, and task types, and generates invoices from billable time through the workspace's own Stripe connection. It also links tasks to Linear, Notion, Teamwork, and Asana and tracks AI agent sessions and costs.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>