Install Jentic One Beta

Connect the Uptimely API to your agent

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

Create and update monitors, then read a monitor's status history over time

Send alerts and change an alert's state as a situation evolves

Declare incidents, change their state, and save a postmortem when resolved

Build status pages and choose which monitors they show

Mute and unmute a monitor's alerting during planned maintenance

GET STARTED

Start building with Uptimely API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Uptimely API for, with concrete tasks.

★ Agent-Managed Uptime Monitoring

An AI agent stands up monitoring for a new service without a human clicking through a dashboard. It creates a monitor, reads the status history to confirm checks are running, and registers a webhook endpoint so downstream systems hear about state changes. Jentic exposes each Uptimely operation with its input schema so the agent sets the check interval and target correctly on the first call.

Create an HTTP monitor for a homepage URL, read its status history to confirm it is checking, and register a webhook endpoint for its state changes

Incident Lifecycle Automation

An on-call workflow declares an incident the moment a monitor goes down and walks it through to resolution. The Uptimely API declares the incident, changes its state as responders work, and saves a postmortem once service is restored, while the current on-call lookup tells the agent who to notify. Alerts move through their own states alongside the incident.

Declare an incident for a failing monitor, look up who is on call now, then change the incident state as it is worked

Public Status Page Updates

A team keeps customers informed by surfacing the right monitors on a public status page. The Uptimely API creates a status page, adds monitor resources to it, and removes them when a service is retired, so the page reflects what is actually watched. Monitors can be muted during planned maintenance so the page does not alarm needlessly.

Create a status page, show a monitor on it, then mute that monitor's alerting for a scheduled maintenance window

Key Endpoints

34 endpoints — the uptimely api creates uptime monitors, declares and tracks incidents, and drives public status pages for people and agents alike.

METHOD

PATH

DESCRIPTION

GET

/v1/monitors

List monitors

POST

/v1/monitors

Create a monitor

GET

/v1/monitors/{monitor_id}/status-history

Read a monitor's status history

POST

/v1/incidents

Declare an incident

POST

/v1/incidents/{incident_id}/state-changes

Change an incident's state

POST

/v1/status-pages

Create a status page

GET

/v1/on-call/current

Look up who is on call now

GET

/v1/monitors

List monitors

POST

/v1/monitors

Create a monitor

GET

/v1/monitors/{monitor_id}/status-history

Read a monitor's status history

POST

/v1/incidents

Declare an incident

POST

/v1/incidents/{incident_id}/state-changes

Change an incident's state

POST

/v1/status-pages

Create a status page

GET

/v1/on-call/current

Look up who is on call now

Why Jentic?

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

Setup

Wiring the Uptimely API by hand means managing its bearer token, learning the monitor, incident, and alert state models, and keeping webhook signing secrets in sync. Through Jentic you install once, import Uptimely from the API Directory, store the token once, and your agent calls it.

Permission scoping

Uptimely puts the monitor id and status-page id in the URL path (/v1/monitors/{monitor_id}, /v1/status-pages/{status_page_id}), so a rule can pin your agent to the monitors and status pages you name and the operations you pick. You choose the operations it may call, so deleting a monitor or a status page is not included unless you add them.

Credential isolation

Your Uptimely 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 'create a monitor' or 'declare an incident', and Jentic returns the matching Uptimely operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Uptimely API through Jentic.

What authentication does the Uptimely API use?

The Uptimely API authenticates with a bearer token in the Authorization header, in the uptimely_live_ key format, per its OpenAPI spec. Through Jentic that token is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in your agent's prompt or logs.

Can I declare incidents with the Uptimely API?

Yes. You declare an incident, change its state through the state-changes operation as responders work, and save a postmortem once it is resolved. The current on-call lookup tells your agent who is responsible at the moment the incident opens.

What are the rate limits for the Uptimely API?

The Uptimely OpenAPI spec does not publish fixed rate limits. The usage endpoint returns your current project usage, so your agent can read consumption before sending more requests rather than guessing a ceiling.

Is there an Uptimely MCP server?

You do not need an MCP server to give your agent the Uptimely API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls its operations. Operations are discovered on demand, so your agent's context stays lean instead of loading a full tool list up front.

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

Yes. Write a rule that allows only the monitor-read and incident operations, so the agent can watch monitors and declare or update incidents but cannot delete a monitor or change your status pages, and every call it makes is logged. Deletion stays out of the allowed set until you add it.

How do I create a monitor with the Uptimely API through Jentic?

Search Jentic for 'create an uptime monitor', and it returns the Uptimely monitor-create operation with its input schema. Your agent posts the target URL and check interval, then reads the status history to confirm checks are running. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getuptimely Uptimely API

AI ReadinessAI-Ready (A)81/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer34 EndpointsREST

For Agents

Create uptime monitors, read their status history, declare and update incidents, send alerts, and manage public status pages and webhook endpoints.

Use for: Create an HTTP monitor for my homepage, Declare an incident for a degraded service, List all open incidents, Mute alerting on a monitor during maintenance

Not supported: Does not handle application performance tracing, log aggregation, or server provisioning. Use for uptime monitoring, incidents, alerts, and status pages only.

The Uptimely API creates uptime monitors, declares and tracks incidents, and drives public status pages for people and agents alike. It records each monitor's status history, sends alerts and moves them through states, and lets you save an incident postmortem once a situation is resolved. Webhook endpoints with rotatable signing secrets, on-call lookups, and per-project usage round out the monitoring surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

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

100%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: ASignals: 4

92%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

59%

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: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Uptimely API to your agent

Capabilities

Start building with Uptimely API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getuptimely Uptimely API

Jentic AI Readiness Score

Uptimely 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