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 API contracts indexed on the APIs.io network, including Incidents API, Maintenance API, Monitors API, and 4 more. Tagged areas include Uptime Monitoring, Status Pages, Incident Management, Observability, and On-Call.

The Hyperping catalog on APIs.io includes 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

28.3/100 thin ▬ flat Agent 19/100 agent aware Front door AI 2/6 trace Heartbeat 85/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

2 published contracts

Uptime Monitoring Status Pages Incident Management Observability On-Call

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

SaaS Platform Operations Management

BC-4220

Health ChecksIncidentsMonitorsOutages

POST /v1/monitors POST /monitors POST /v1/healthchecks POST /healthchecks

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 28.3/100 · thin

Contract Quality 8.8 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 1.2 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.4 / 9

Discoverability 5.0 / 8

Regulatory Posture 1.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/hyperping/"><img src="https://apis.io/badge/hyperping/card.svg" alt="Hyperping on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 32.1 — up to +13.6 composite points
Contract Quality scores 46.8 — up to +13.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/hyperping/apis.yml: open an issue on github.com/api-evangelist/hyperping to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Hyperping is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.

status pagecapability map5 features checked 2026-09-25 · rubric v0.22.0

Hyperping moves one Kin Score check, status_page_present (6 of 38 operational-transparency points), once the provider declares the page as a StatusPage in apis.yml. Unlike several rivals it earns the check even on the free plan’s hosted subdomain: *.hyperping.app returns a real 404 for nonsense paths, so the pointer grades live. Its status.json endpoint, subscriber feeds and MCP server are useful but score nothing for the provider.

Operational Transparency6.0 of 38 pts

Check	Earns	Through
Status page Operational TransparencyBinary check, cleared in full on any plan. The only check the status-page area touches.	6.0 of 6	Hosted status page (hyperping subdomain free, custom domain on paid plans)

Across 8977 providers that publish a contract, adopting Hyperping would move 6390. Median lift: composite +2.0 (90th percentile +2.1), agent readiness +0.0 (+0.0). Conditional rows excluded.

What Hyperping ships that earns nothing (1)

Hyperping MCP server — It serves the provider’s team their Hyperping monitoring data; the dimension reads an MCP server for the provider’s own API, described in its mcp/ manifest.

A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership can. The rating is not for sale → · Full vendor facets artifact

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 7

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

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.

Hyperping Health Checks API

Cron job and scheduled task monitoring

Scroll for all 7

Open Collections 8

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

Hyperping Healthchecks API

OPEN COLLECTION

Hyperping Healthchecks Incidents API

OPEN COLLECTION

Hyperping Healthchecks Maintenance API

OPEN COLLECTION

Hyperping Healthchecks Monitors API

OPEN COLLECTION

Hyperping Healthchecks Outages API

OPEN COLLECTION

Hyperping Healthchecks Reports API

OPEN COLLECTION

Hyperping Healthchecks Status Pages API

OPEN COLLECTION

Hyperping API

OPEN COLLECTION

Scroll for all 8

Hyperping API pricing

Not yet checked against Hyperping's own pricing page. Compiled by API Evangelist on 2026-06-21 from hyperping.com/pricing; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free free	Free
Essentials subscription	—
Pro subscription	—
Business subscription	—
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

API Requests: see provider documentation requests
Monitors: per plan (20 Free / 50 Essentials / 100 Pro / 1000 Business) monitors
Status Pages: per plan (1 / 1 / 3 / 10) status pages

Compiled by API Evangelist, not yet checked against Hyperping's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Hyperping Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Hyperping Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Hyperping

SLA

FinOps 1

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

Hyperping Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Hyperping — hyperping go rules

0 rules ·

SPECTRAL

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

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

VendorFacets

VendorFacets

Source (apis.yml)

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
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  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-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
- aid: hyperping:hyperping-health-checks-api
  name: Hyperping Health Checks API
  description: Cron job and scheduled task monitoring
  humanURL: https://hyperping.com/docs/api/monitors
  baseURL: https://api.hyperping.io
  tags:
  - Health Checks
  properties:
  - type: OpenAPI
    url: openapi/hyperping-health-checks-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: CapabilityMap
  url: capabilities/hyperping-capability-edges.yml
  name: Hyperping Business Capability Map
- type: VendorFacets
  url: vendor-facets/hyperping-vendor-facets.yml
- 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
- type: SpectralRules
  url: https://github.com/hyperping/hyperping-go/blob/7be4590be32b4c81669d41d45bfd335f5ab828b0/.spectral.yaml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Hyperping API — frequently asked questions

Does Hyperping have an API?

Yes. APIs.io lists 7 APIs from Hyperping, including Hyperping Incidents API, Hyperping Maintenance API and Hyperping Monitors API, and 4 more.

Is there an OpenAPI specification for the Hyperping API?

Yes. APIs.io indexes 7 OpenAPI specifications for Hyperping, each linked for download from this page.

How do I authenticate with the Hyperping API?

Hyperping uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Hyperping Authentication.

How much does the Hyperping API cost?

APIs.io lists 5 pricing plans for Hyperping, with each plan's price, limits and inclusions under Pricing on this page.

Is the Hyperping API ready for AI agents?

Hyperping has a Kin Score of 28.3 out of 100 (thin) and an Agent Readiness score of 19.3 (agent-aware), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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

Hyperping

What this lets a business do 1

What adopting Hyperping moves on the Kin Score 1

Standards implemented 1

APIs 7

Open Collections 8

Hyperping API pricing

Rate limits

Pricing Plans 1

Rate Limits 1

Service Levels 1

FinOps 1

Spectral Rules 1

Security Posture 2

Agentic Access 1

Documentation 1

Agent Surfaces 1

Design & Contract 1

Build 1

Access & Security 2

Operate 1

Commercial 2

Company 3

Other 2

Source (apis.yml)

Hyperping API — frequently asked questions

Does Hyperping have an API?

Is there an OpenAPI specification for the Hyperping API?

How do I authenticate with the Hyperping API?

How much does the Hyperping API cost?

Is the Hyperping API ready for AI agents?

MCP server

Tools for providers

Call it yourself

Get an API key