GETPing API

Name: GETPing API
Brand: GETPing API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey8 EndpointsREST

For Agents

Run on-demand pings, manage long-running URL monitors, and pull response-time history for status pages and uptime alerting workflows.

Connect the GETPing API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GETPing 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 GETPing API.

Run an on-demand ping against any HTTP URL and capture latency and status

Submit a batch ping job to test multiple URLs in a single request

Pull historical ping results for a monitor to compute uptime percentages

GET STARTED

Start building with GETPing API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use GETPing API for, with concrete tasks.

★ Synthetic uptime monitoring for a SaaS

GETPing acts as the synthetic-monitoring backbone for small teams that want pings from outside their infrastructure without standing up Prometheus or paying for a full APM suite. Register a monitor for each critical URL, then query the history endpoint from a dashboard or Slack bot to surface incidents within the polling interval.

Create a monitor for https://api.example.com/health with a 60-second interval and post any failed checks to Slack #ops

Pre-deploy reachability check

CI pipelines call the on-demand ping endpoint after a deployment to confirm the new build's public URLs respond before flipping traffic. Batch ping covers multiple regional endpoints in a single call, keeping the pipeline step under a few seconds.

Run a batch ping on the production, staging, and EU-region URLs and fail the deploy if any return a non-2xx status

Incident response co-pilot

An on-call agent receives an alert and asks Jentic 'is the payments API still down?' The agent routes the question to GETPing, runs an on-demand ping, and returns latency plus the last-hour history pulled from the monitor's records. This lets responders confirm or rule out an outage without opening another tab.

Ping https://payments.example.com, fetch the last hour of monitor history, and summarise success rate and median latency

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for getping api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/ping

Ping a single URL on demand

POST

/ping

Batch ping multiple URLs

POST

/monitors

Create a recurring URL monitor

GET

/monitors

List configured monitors

GET

/monitors/{monitorId}/history

Retrieve monitor result history

DELETE

/monitors/{monitorId}

Remove a monitor

GET

/ping

Ping a single URL on demand

POST

/ping

Batch ping multiple URLs

POST

/monitors

Create a recurring URL monitor

GET

/monitors

List configured monitors

GET

/monitors/{monitorId}/history

Retrieve monitor result history

DELETE

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

GETPing API keys are stored encrypted in the Jentic vault. Agents receive a scoped credential reference and the raw X-API-Key header value never enters the agent's context.

Intent-based discovery

Agents search by intent such as 'check if a URL is up' and Jentic returns the matching GETPing operation along with its input schema.

Time to first call

Direct GETPing integration: a few hours to wire auth and history pagination. Through Jentic: under 15 minutes to search, load, and execute.

FAQs

Specific to using GETPing API through Jentic.

Why is there no official OpenAPI spec for GETPing API?

GETPing does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GETPing API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the GETPing API use?

GETPing uses an API key sent as the X-API-Key header. Through Jentic the key is stored encrypted in the vault and injected per request, so the raw key never lands in your agent's prompt or logs.

Can I batch ping multiple URLs in one call?

Yes. POST /ping accepts an array of URLs and returns one result per target, which is useful for regional reachability checks or pre-deploy smoke tests against a list of endpoints.

What are the rate limits for the GETPing API?

The OpenAPI spec does not declare specific rate limits. Treat it as a polite-use API: avoid sub-second polling intervals on monitors and prefer the monitor history endpoint over repeatedly hitting GET /ping for the same URL.

How do I retrieve monitor history through Jentic?

Search Jentic for 'get monitor history', load the GET /monitors/{monitorId}/history schema, then execute with your monitor identifier. The response gives you the time series you can chart on a status page.

Can I update a monitor's URL without losing history?

Yes. PUT /monitors/{monitorId} updates the monitor in place — its identifier and accumulated history are preserved while the polled URL or interval changes.

GETPing API

Connect the GETPing API to your agent

Capabilities

Start building with GETPing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs