Install Jentic One Beta

Connect the Hyperping API to your agent

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

Create a status page with a subdomain or custom hostname, theme, accent colour, languages, and logo

Publish an outage or incident on one or more status pages with affected components

Add investigating, identified, monitoring, or resolved updates to an incident's public timeline

Schedule maintenance windows for chosen monitors and status pages with advance notification settings

GET STARTED

Start building with Hyperping API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hyperping API for, with concrete tasks.

★ Status page communication by an agent through Jentic

A developer's agent keeps the public status page current during an incident: it opens the incident, then adds timeline updates as the team reports progress. Through Jentic it finds the incident operations by intent, the Hyperping key is injected by the developer's own Jentic One instance, and a rule can pin it to one incident id so it cannot edit other incidents or the page settings.

Call POST /v3/incidents with type incident, a title of 'Payments degraded', and the public status page id in statuspages, then call POST /v3/incidents/{uuid}/updates with type monitoring and text 'A fix is deployed and we are watching error rates'

Planned maintenance notices

Announce planned work and keep it from paging anyone. A maintenance window needs a name, start_date, end_date, and the monitors it covers, and can also list status pages, a public title and updates, and notification settings through notificationOption and notificationMinutes.

Call POST /v1/maintenance-windows with name 'Database upgrade', start_date 2026-11-07T02:00:00Z, end_date 2026-11-07T04:00:00Z, the two API monitor ids in monitors, and the public status page id in statuspages

Launch a branded status page

Stand up a status page for a new product. The create call takes a name and a subdomain or hostname plus branding such as theme, font, accent_color, logo, and favicon; the spec notes the page is public as soon as it exists unless authentication is set, so set that first if it should stay private.

Call POST /v2/statuspages with name 'Acme Status', subdomain acme-status, hostname status.acme.com, accent_color #4F46E5, and theme light, then read it back with GET /v2/statuspages/{uuid}

Outage cleanup and follow-up

Close the loop after an incident. List outages filtered to resolved or ongoing and by manual or monitor type, resolve any left open, and pull the affected monitor's report for SLA and MTTR to include in the post-incident review.

Call GET /v2/outages with status ongoing, POST /v2/outages/{uuid}/resolve for each one the team confirmed fixed, then GET /v2/reporting/monitor-reports/{uuid} for the affected monitor

Key Endpoints

38 endpoints — the hyperping api, served from api.

METHOD

PATH

DESCRIPTION

POST

/v3/incidents

Create a status page incident

POST

/v3/incidents/{uuid}/updates

Add an incident timeline update

PUT

/v3/incidents/{uuid}

Update an incident

POST

/v2/statuspages

Create a status page

PUT

/v2/statuspages/{uuid}

Update a status page

POST

/v1/maintenance-windows

Schedule a maintenance window

GET

/v2/outages

List detected outages

POST

/v1/healthchecks

Create a cron healthcheck

POST

/v3/incidents

Create a status page incident

POST

/v3/incidents/{uuid}/updates

Add an incident timeline update

PUT

/v3/incidents/{uuid}

Update an incident

POST

/v2/statuspages

Create a status page

PUT

/v2/statuspages/{uuid}

Update a status page

POST

/v1/maintenance-windows

Schedule a maintenance window

GET

/v2/outages

List detected outages

POST

/v1/healthchecks

Create a cron healthcheck

Why Jentic?

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

Setup

Wiring the Hyperping API by hand means issuing a project key, sending it as a bearer token to api.hyperping.io, and learning that status page incidents sit under /v3 while status pages and outages sit under /v2 and monitors under /v1. Through Jentic you install once, import Hyperping from the API Directory, store the key once, and your agent calls it.

Permission scoping

Hyperping puts the incident, status page, and monitor id in the URL path (/v3/incidents/{uuid}, /v2/statuspages/{uuid}), so a rule can pin your agent to one incident or one status page. You choose the operations it may call, so deleting incidents, status pages, or monitors is not included unless you add it.

Credential isolation

Your Hyperping API 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 'post a status page update' or 'schedule maintenance', and Jentic returns the matching Hyperping operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Hyperping API through Jentic.

What authentication does the Hyperping API use?

The Hyperping OpenAPI spec declares HTTP bearer authentication. You create the API key on your project's developers page in the Hyperping app and send it in the Authorization header to api.hyperping.io. With Jentic, your own Jentic One instance keeps the key encrypted and adds it to each call, so the agent does not hold it.

How do I post updates to a Hyperping status page incident?

Create the incident with POST /v3/incidents, giving a title and a type of outage or incident, then add timeline entries with POST /v3/incidents/{uuid}/updates. Each update carries a date, localized text, and a type of investigating, identified, update, monitoring, or resolved.

Is a new Hyperping status page public straight away?

Yes, according to the spec: POST /v2/statuspages creates a page that is public as soon as it exists, unless authentication is set. When editing later, note that sending sections in PUT /v2/statuspages/{uuid} replaces every section, so start from the GET response.

What are the rate limits for the Hyperping API?

Rate limits are not stated in the Hyperping OpenAPI spec. Check Hyperping's documentation at https://hyperping.com for the current limits on your plan.

How do I schedule maintenance with the Hyperping API through Jentic?

Search Jentic for 'schedule a maintenance window' to get POST /v1/maintenance-windows, then send the required name, start_date, end_date, and monitors, plus statuspages if the notice should appear publicly. To run it on your own infrastructure, install Jentic One from its GitHub repo and store your Hyperping key once.

Is there a Hyperping MCP server?

You don't need an MCP server to give your agent Hyperping. Jentic connects it directly from the API Directory: import it, store your key once, and your agent reaches the incident, status page, and monitor operations you allow without extra tool definitions in its context.

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

Yes. For example, allow only POST /v3/incidents/{uuid}/updates and PUT /v3/incidents/{uuid} for the open incident's id, so the agent can post progress and resolve that one incident but cannot create new ones, change status page settings, or delete monitors. Your Jentic One instance logs the calls it makes.

Hyperping API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer38 EndpointsREST

For Agents

Publish and update Hyperping status page incidents, build and restyle status pages, schedule maintenance windows, manage uptime monitors and cron healthchecks, and act on detected outages.

Use for: Post an incident on our status page saying payments are degraded, Add a monitoring update to the open incident, Mark the status page incident as resolved, Schedule maintenance for Saturday 02:00 to 04:00 UTC on the API monitors

Not supported: Does not send customer email or SMS campaigns, host a help center, or store application logs and traces. Use for Hyperping status pages, incidents, maintenance windows, monitors, healthchecks, and outage handling only.

The Hyperping API, served from api.hyperping.io, runs a project's uptime checks and the public status pages that report them. Status page calls create and restyle pages with a subdomain or custom hostname, theme, languages, and sections, and incident calls publish outages or incidents on those pages with localized titles and a timeline of investigating, identified, monitoring, and resolved updates. Behind the page, the API manages HTTP, port, and ICMP monitors, cron healthchecks with ping URLs and grace periods, and detected outages with acknowledge, escalate, and resolve actions. Maintenance windows silence alerts during planned work, and per-monitor reports return SLA and MTTR figures.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

60%

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

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

30%

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: D+Signals: 4

35%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

64%

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

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hyperping API to your agent

Capabilities

Start building with Hyperping API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hyperping API

Jentic AI Readiness Score

Hyperping 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