Hyperping website screenshot

Hyperping

Hyperping is an uptime monitoring and status page platform. Its REST API lets teams programmatically manage HTTP, ping, port, keyword, DNS, and browser monitors, run scheduled-task healthchecks, operate public status pages through incidents and maintenance windows, manage on-call outages, and pull uptime and SLA reporting.

Hyperping publishes 7 APIs on the APIs.io network, including Healthchecks API, Incidents API, Maintenance API, and 4 more. Tagged areas include Uptime Monitoring, Status Pages, Incident Management, Observability, and On-Call.

Hyperping’s developer surface includes authentication, documentation, engineering blog, and 8 more developer resources.

38.2/100 thin ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFreemiumSelf serve⚡ Free to try
1 APIs
Uptime MonitoringStatus PagesIncident ManagementObservabilityOn-Call

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hyperping: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Hyperping Healthchecks API

Cron-style monitors that expect periodic pings from scheduled tasks.

Hyperping Incidents API

Status page incident lifecycle and updates.

Hyperping Maintenance API

Scheduled maintenance windows.

Hyperping Monitors API

Create, retrieve, update, and delete uptime monitors.

Hyperping Outages API

On-call outage acknowledgement, resolution, and escalation.

Hyperping Reports API

Uptime, SLA, and MTTR reporting for monitors.

Hyperping Status Pages API

Public machine-readable status feed for a status page.

Scroll for all 7

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Hyperping API

OPEN COLLECTION

Scroll for all 9

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hyperping Rate Limits

4 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hyperping Authentication

http · 1 scheme

SECURITY

Hyperping Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Hyperping Agentic Access

35 operations · 22 acting

35 operations · 22 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: hyperping
url: https://raw.githubusercontent.com/api-evangelist/hyperping/refs/heads/main/apis.yml
name: Hyperping
kind: company
description: Hyperping is an uptime monitoring and status page platform. Its REST API lets teams programmatically manage HTTP,
  ping, port, keyword, DNS, and browser monitors, run scheduled-task healthchecks, operate public status pages through incidents
  and maintenance windows, manage on-call outages, and pull uptime and SLA reporting.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/hyperping.png
tags:
- Uptime Monitoring
- Status Pages
- Incident Management
- Observability
- On-Call
created: '2026-06-21'
modified: '2026-06-21'
specificationVersion: '0.23'
apis:
- aid: hyperping:hyperping-healthchecks-api
  name: Hyperping Healthchecks API
  description: Cron-style monitors that expect periodic pings from scheduled tasks.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Health Checks
  tags_raw:
  - Healthchecks
  properties:
  - type: OpenAPI
    url: openapi/hyperping-healthchecks-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-incidents-api
  name: Hyperping Incidents API
  description: Status page incident lifecycle and updates.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Incidents
  properties:
  - type: OpenAPI
    url: openapi/hyperping-incidents-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-maintenance-api
  name: Hyperping Maintenance API
  description: Scheduled maintenance windows.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Maintenance
  properties:
  - type: OpenAPI
    url: openapi/hyperping-maintenance-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-monitors-api
  name: Hyperping Monitors API
  description: Create, retrieve, update, and delete uptime monitors.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Monitors
  properties:
  - type: OpenAPI
    url: openapi/hyperping-monitors-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-outages-api
  name: Hyperping Outages API
  description: On-call outage acknowledgement, resolution, and escalation.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Outages
  properties:
  - type: OpenAPI
    url: openapi/hyperping-outages-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-reports-api
  name: Hyperping Reports API
  description: Uptime, SLA, and MTTR reporting for monitors.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Reports
  properties:
  - type: OpenAPI
    url: openapi/hyperping-reports-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
- aid: hyperping:hyperping-status-pages-api
  name: Hyperping Status Pages API
  description: Public machine-readable status feed for a status page.
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io/v1
  tags:
  - Status Pages
  properties:
  - type: OpenAPI
    url: openapi/hyperping-status-pages-api-openapi.yml
  - type: Documentation
    url: https://hyperping.com/docs/api/monitors
  - type: APIReference
    url: https://hyperping.com/docs/api/monitors
  - type: PostmanCollection
    url: collections/hyperping.postman_collection.json
  - type: OpenCollection
    url: collections/hyperping.opencollection.json
  - type: Documentation
    url: https://hyperping.com/docs/status-page/status-page-json
  - type: Documentation
    url: https://hyperping.com/docs/api/incidents
  - type: APIReference
    url: https://hyperping.com/docs/api/incidents
  - type: Documentation
    url: https://hyperping.com/docs/integrations/webhooks
common:
- type: AgenticAccess
  url: agentic-access/hyperping-agentic-access.yml
- type: DomainSecurity
  url: security/hyperping-domain-security.yml
- type: Authentication
  url: authentication/hyperping-authentication.yml
- type: GitHubOrganization
  url: https://github.com/hyperping
- type: LinkedIn
  url: https://www.linkedin.com/company/hyperping
- type: Website
  url: https://hyperping.com/
- type: Documentation
  url: https://hyperping.com/docs
- type: Plans
  url: plans/hyperping-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hyperping-rate-limits.yml
- type: FinOps
  url: finops/hyperping-finops.yml
- url: https://hyperping.com/blog
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/hyperping"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hyperping/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hyperping/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.