canonical: https://jentic.com/apis/watchful.li/watchfulli

# watchful.li

Watchful provides programmatic access to developer tools functionality. The API exposes 59 endpoints.

## For AI agents

Programmatically get a list of audits, get the list of fields. Covers 59 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get a list of audits
- Find audit by ID
- Delete a specific audit
- Set 'ignore updates' for a given extension / site_id
- Monitor Watchful operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get a list of audits', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/audits` | Get a list of audits |
| GET | `/audits/metadata` | Get the list of fields |
| GET | `/audits/{id}` | Find audit by ID |
| DELETE | `/audits/{id}` | Delete a specific audit |
| GET | `/extensions` | Get a list Extensions |
| GET | `/extensions/metadata` | Get the list of fields |
| POST | `/extensions/{id}/ignore` | Set 'ignore updates' for a given extension / site_id |
| POST | `/extensions/{id}/unignore` | Remove 'ignore updates' for a given extension |

## Key resources

- **audits** — Operations about audits
- **extensions** — Operations about extensions
- **feedbacks** — Operations about feedbacks
- **logs** — Operations about logs
- **reports** — Create reports in PDF

## AI readiness

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.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 93 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/watchful.li/watchfulli/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Watchful API?

Yes. Because you run Jentic One yourself, your own rules decide which Watchful operations and credentials the agent may use. You can allow read operations like GET /audits and GET `/audits/{id}` plus a targeted action such as ignoring an extension via POST `/extensions/{id}/ignore`, while leaving a destructive call like DELETE `/audits/{id}` out unless you add it. Since the resource id sits in the URL path for `/audits/{id}` and `/extensions/{id}`, you can also pin the agent to a single audit or extension.