Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the watchful.li, 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%2Fwatchful.li%2Fwatchfulli" | 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%2Fwatchful.li%2Fwatchfulli" | 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 watchful.li API.
Get a list of audits
Find audit by ID
Delete a specific audit
Set 'ignore updates' for a given extension / site_id
GET STARTED
For Agents
Programmatically get a list of audits, get the list of fields. Covers 59 operations.
Use for: I need to a list of audits, I want to the list of fields, Search for audit by id, Find all a specific audit
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Watchful provides programmatic access to developer tools functionality. The API exposes 59 endpoints.
Monitor Watchful operational status and events
Patterns agents use watchful.li API for, with concrete tasks.
★ Developer Tools Operations
Use the Watchful to perform developer tools operations programmatically. The API provides 59 endpoints covering core functionality including get a list of audits, get the list of fields, find audit by id.
Call GET /audits to get a list of audits
Automated audits Management
Automate audits operations by combining multiple Watchful endpoints. Agents can get the list of fields and then find audit by id in a single workflow.
Call GET /audits/metadata to get the list of fields, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Watchful 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 none tokens manually.
Search Jentic for 'get a list of audits', load the operation schema, and execute with Jentic-managed credentials
59 endpoints — watchful provides programmatic access to developer tools functionality.
METHOD
PATH
DESCRIPTION
/audits
Get a list of audits
/audits/metadata
Get the list of fields
/audits/{id}
Find audit by ID
/audits/{id}
Delete a specific audit
/extensions
Get a list Extensions
/extensions/metadata
Get the list of fields
/extensions/{id}/ignore
Set 'ignore updates' for a given extension / site_id
/extensions/{id}/unignore
Remove 'ignore updates' for a given extension
/audits
Get a list of audits
/audits/metadata
Get the list of fields
/audits/{id}
Find audit by ID
/audits/{id}
Delete a specific audit
/extensions
Get a list Extensions
/extensions/metadata
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the watchful.li API by hand means pointing at the watchful.li/api/v1 host and authenticating each request yourself. Through Jentic you install once, import the watchful.li API from the API Directory, store your credential once, and your agent calls it.
Permission scoping
The watchful.li API puts the resource id in the URL path (/audits/{id} and /extensions/{id}), so a rule can pin your agent to one audit or extension. You choose the operations it may call, so you can allow reading audits and ignoring an extension while a destructive one like deleting an audit is not included unless you add it.
Credential isolation
Your watchful.li credential 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 'get a list of audits' or 'ignore an extension', and Jentic returns the matching watchful.li API 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using watchful.li API through Jentic.
What authentication does the Watchful use?
The Watchful uses no authentication. 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 get a list of audits with the Watchful?
Yes. Use the GET /audits endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Watchful?
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 get a list of audits through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get a list of audits'. Jentic returns the matching Watchful operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Watchful have?
The Watchful exposes 59 endpoints covering audits, extensions, feedbacks operations.
Get the list of fields
/extensions/{id}/ignore
Set 'ignore updates' for a given extension / site_id
/extensions/{id}/unignore
Remove 'ignore updates' for a given extension