Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Time etc 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%2Ftimeetc.co.uk%2Ftimeetc" | 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%2Ftimeetc.co.uk%2Ftimeetc" | 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 Time etc API.
Login and get auth token
Get tasks created in last 15 minutes
Create a new task
Query and filter Time etc API records by parameters
Monitor Time etc API operational status and events
GET STARTED
Patterns agents use Time etc API for, with concrete tasks.
★ Productivity Operations
Use the Time etc API to perform productivity operations programmatically. The API provides 7 endpoints covering core functionality including login and get auth token, get tasks created in last 15 minutes, create a new task.
Call POST /authorization/zapier to login and get auth token
Automated Authentication Management
Automate authentication operations by combining multiple Time etc API endpoints. Agents can get tasks created in last 15 minutes and then create a new task in a single workflow.
Call GET /zapier/new-tasks to get tasks created in last 15 minutes, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Time etc 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 'login and get auth token', load the operation schema, and execute with Jentic-managed credentials
7 endpoints — time etc virtual assistant platform api for task management, comments, and team operations.
METHOD
PATH
DESCRIPTION
/authorization/zapier
Login and get auth token
/zapier/new-tasks
Get tasks created in last 15 minutes
/zapier/create-new-task
Create a new task
/zapier/new-comments
Get comments created in last 15 minutes
/zapier/logged-times
Get logged times in last 15 minutes
/zapier/completed-tasks
Get tasks completed in last 15 minutes
/zapier/team
Get all assistants in team
/authorization/zapier
Login and get auth token
/zapier/new-tasks
Get tasks created in last 15 minutes
/zapier/create-new-task
Create a new task
/zapier/new-comments
Get comments created in last 15 minutes
/zapier/logged-times
Get logged times in last 15 minutes
/zapier/completed-tasks
Get tasks completed in last 15 minutes
/zapier/team
Get all assistants in team
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Time etc API by hand means setting its X-Auth-Token header, following the Zapier-style task and comment endpoints, and handling retries yourself. Through Jentic you install once, import Time etc from the API Directory, store the token once, and your agent calls it.
Permission scoping
Time etc addresses tasks and comments through the request body rather than the URL path, so scope the agent by the operations it needs, such as listing new tasks or creating a task. You choose that set, so operations you do not name stay unavailable.
Credential isolation
Your Time etc 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 'list new tasks' or 'log a completed task', and Jentic returns the matching Time etc 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 Time etc API through Jentic.
What authentication does the Time etc API use?
The Time etc API uses an API key passed in the `X-Auth-Token` 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 login and get auth token with the Time etc API?
Yes. Use the POST /authorization/zapier endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Time etc 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 login and get auth token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login and get auth token'. Jentic returns the matching Time etc API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Time etc API have?
The Time etc API exposes 7 endpoints covering authentication, tasks, comments operations.
Can I limit what my agent is allowed to do with the Time etc API?
Yes. Because you run Jentic One yourself, your own rules decide which Time etc operations and credentials the agent may use, so you can allow only the calls it needs, such as listing new tasks or creating a task, while withholding others like reading comments, logged times, completed tasks, or the team roster. Time etc addresses tasks and comments through the request body rather than the URL path, so you scope the agent by the specific operations you name rather than by path patterns. Any operation you do not grant stays unavailable to the agent, and your stored token is injected only for the calls you allow.
For Agents
Programmatically login and get auth token, get tasks created in last 15 minutes. Covers 7 operations with apiKey authentication.
Use for: I need to login and get auth token, I want to tasks created in last 15 minutes, Search for a new task, Find all comments created in last 15 minutes
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Time etc virtual assistant platform API for task management, comments, and team operations. The API exposes 7 endpoints secured with apiKey authentication.