Install Jentic One Beta

Connect the CronAlive API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CronAlive 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%2Fcronalive.com%2Fcronalive" | sh

Step 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%2Fcronalive.com%2Fcronalive" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with CronAlive API.

Create and configure heartbeat checks for scheduled jobs and services

Read a check's recent pings and its status flips over time

Pause and resume monitoring on a check

Manage the notification integrations that deliver alerts

Fetch the current fallback list of ping domains for SDKs

GET STARTED

Start building with CronAlive API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CronAlive API for, with concrete tasks.

★ Cron Job Heartbeat Monitoring

An agent sets up dead-man's-switch monitoring for a scheduled job. It creates a check that expects a ping on a cadence, and CronAlive raises an alert through the configured integrations when an expected ping does not arrive, so a silently failed cron job is caught rather than missed.

Call POST /checks to create a heartbeat check with a cadence, then GET /checks/{uuid}/pings to confirm pings are arriving

Incident Triage from Status Flips

When an on-call agent investigates an alert, it reads a check's recent status flips and pings to see when the service went down and whether it has recovered. Pausing monitoring during planned maintenance keeps the flip history clean of expected outages.

Call GET /checks/{uuid}/flips to read status changes, then POST /checks/{uuid}/pause during maintenance

AI Agent Integration via Jentic

An AI agent reaches the CronAlive API through Jentic without wiring the bearer project key itself. It searches by intent, receives the matching operation and its input schema, and executes with the credential injected at run time, creating checks and reading their health as part of a larger operations workflow.

Search Jentic for 'create a heartbeat check', load the POST /checks schema, and execute it with Jentic-managed credentials

Key Endpoints

14 endpoints — the cronalive api monitors scheduled jobs and services with heartbeat checks that expect a ping on a cadence and raise an alert when one is missed.

METHOD

PATH

DESCRIPTION

GET

/checks

List checks of the key's project

POST

/checks

Create a check

GET

/checks/{uuid}

Get a check

PATCH

/checks/{uuid}

Update a check

POST

/checks/{uuid}/pause

Pause monitoring

GET

/checks/{uuid}/pings

Recent pings for a check

GET

/checks/{uuid}/flips

Recent status changes

GET

/integrations

List integrations

GET

/checks

List checks of the key's project

POST

/checks

Create a check

GET

/checks/{uuid}

Get a check

PATCH

/checks/{uuid}

Update a check

POST

/checks/{uuid}/pause

Pause monitoring

GET

/checks/{uuid}/pings

Recent pings for a check

GET

/checks/{uuid}/flips

Recent status changes

GET

/integrations

List integrations

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring CronAlive by hand means sending its bearer project key, choosing between read-only and read-write keys, and honoring the Retry-After header on rate limits yourself. Through Jentic you install once, import CronAlive from the API Directory, store the key once, and your agent calls it.

Permission scoping

CronAlive puts the check id in the URL path (/checks/{uuid}), so a rule can pin your agent to one check and the operations you pick. You choose that set, so destructive actions like deleting a check or an integration are not included unless you add them.

Credential isolation

Your CronAlive key 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 'create a heartbeat check' or 'read a monitor's status flips', and Jentic returns the matching CronAlive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CronAlive API through Jentic.

What authentication does the CronAlive API use?

The CronAlive API authenticates with a bearer project key in the Authorization header per its OpenAPI spec, using ca_rw_ read-write or ca_ro_ read-only keys, where read-only keys may call only GET endpoints. The ping-domains endpoint is public. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

What are the rate limits for the CronAlive API?

The OpenAPI spec states a limit of 600 requests per minute per key, returning a 429 with a Retry-After header on excess. An agent can honor the Retry-After value to back off rather than retrying blindly.

Can I read a check's status history with the CronAlive API?

Yes. The pings endpoint returns a check's recent pings and the flips endpoint returns its status changes over time, so an agent can see when a service went down and whether it recovered. Both return structured JSON an agent can act on directly.

How do I create a heartbeat check through Jentic with the CronAlive API?

Search Jentic for 'create a heartbeat check', and it returns the CronAlive check-creation operation with its input schema. Load the schema and execute POST /checks with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. CronAlive puts the check id in the URL path, so a rule can pin your agent to one check and the read operations you pick, such as its pings and flips. Deleting a check or changing an integration stays out of reach unless you grant it, and every call runs through your own instance where it is logged.

CronAlive API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer14 EndpointsREST

For Agents

Create and configure heartbeat checks, read their recent pings and status flips, pause or resume monitoring, and manage alert integrations. Authenticated with a bearer project key across 14 operations.

Use for: Create a heartbeat check for a nightly cron job, List the checks in my project, Get the recent pings for a check, Pause monitoring on a check during maintenance

Not supported: Does not handle log aggregation, metric dashboards, or application performance tracing. Use for heartbeat and uptime monitoring of scheduled jobs and services only.

The CronAlive API monitors scheduled jobs and services with heartbeat checks that expect a ping on a cadence and raise an alert when one is missed. It creates and configures checks, reads their recent pings and status flips, pauses and resumes monitoring, and manages the notification integrations that deliver alerts. Read-only and read-write project keys scope what a caller can do, and a fallback list of ping domains is published for SDKs.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

19%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

32%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

20%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CronAlive API to your agent

Capabilities

Start building with CronAlive API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CronAlive API

Jentic AI Readiness Score

CronAlive API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness