Ping.ie Network Diagnostics API

Name: Ping.ie Network Diagnostics API
Brand: Ping.ie Network Diagnostics API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey12 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Ping.ie Network Diagnostics API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ping.ie Network Diagnostics 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Ping.ie Network Diagnostics API.

Execute ICMP ping tests against any IP address or hostname with configurable packet count and timeout

Run traceroute operations to map network paths and identify routing bottlenecks between locations

Perform DNS lookups supporting A, AAAA, MX, TXT, CNAME, and NS record queries

GET STARTED

Start building with Ping.ie Network Diagnostics API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Ping.ie Network Diagnostics API, keeping it validated and agent-ready. Ping.ie is a comprehensive network diagnostic and monitoring service that provides developers with tools to test connectivity, measure latency, check DNS resolution, and monitor endpoint availability from multiple geographic locations. The API exposes twelve endpoints covering ping tests, traceroute operations, DNS lookups, port scanning, SSL certificate validation, and continuous uptime monitoring, designed for embedding in DevOps workflows, incident response systems, and infrastructure health dashboards.

Use Cases

Patterns agents use Ping.ie Network Diagnostics API for, with concrete tasks.

★ Multi-region latency testing for CDN selection

Ping.ie enables DevOps teams to measure response times from multiple geographic probe locations before selecting CDN endpoints or regional server deployments. Run concurrent ping tests from Europe, North America, and Asia-Pacific nodes, then analyze the latency distribution to determine optimal content delivery points. The API returns per-location metrics in a single response, eliminating the need to maintain distributed testing infrastructure.

Ping example.com from Dublin, New York, and Singapore locations and return the average latency for each region

Automated SSL certificate expiration monitoring

Security teams integrate Ping.ie into compliance dashboards to track SSL certificate expiration across their domain portfolio. The API checks certificate validity, chain completeness, and expiration dates for any HTTPS endpoint, then surfaces certificates expiring within 30 days. Combine with the monitor endpoints to receive automated alerts when certificates need renewal, preventing unexpected expiration incidents.

Check the SSL certificate for https://secure.example.com and alert if it expires within 30 days

Incident response network diagnostics

On-call engineers invoke Ping.ie during incident response to quickly diagnose connectivity issues without switching tools. An AI agent receives a report that 'users in Europe cannot reach the API,' then executes ping tests, traceroutes, and DNS lookups from European probe locations to determine whether the issue is DNS propagation, routing, or server availability. The structured API response feeds directly into incident timeline documentation.

Run a traceroute from Dublin to api.example.com, check DNS resolution, and ping the resolved IP to diagnose a reported European connectivity issue

Continuous uptime monitoring for SLA tracking

Product teams use Ping.ie monitors to track availability against service-level agreements and display uptime percentages on public status pages. Create monitors for critical endpoints with 60-second check intervals, then query the history API to compute hourly, daily, and monthly uptime metrics. The API includes downtime incident details showing exact timestamps and failure reasons, supporting root-cause analysis and SLA reporting.

Create a monitor for https://api.example.com/health checking every 60 seconds, then retrieve the last 30 days of uptime data for SLA reporting

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for ping.

METHOD

PATH

DESCRIPTION

POST

/ping

Execute a ping test against a target host from specified locations

POST

/traceroute

Run a traceroute to map the network path to a destination

POST

/dns/lookup

Query DNS records for a domain with specified record type

POST

/port/check

Check if a TCP or UDP port is open and measure connection time

GET

/ssl/validate

Validate SSL certificate for an HTTPS endpoint

POST

/monitors

Create a new uptime monitor with configurable interval and locations

GET

/monitors

List all configured uptime monitors

GET

/monitors/{monitorId}

Retrieve details for a specific monitor

PUT

/monitors/{monitorId}

Update monitor configuration preserving history

DELETE

/monitors/{monitorId}

Remove a monitor and its historical data

GET

/monitors/{monitorId}/history

Retrieve check results and downtime incidents for a monitor

GET

/locations

List available probe locations for distributed testing

POST

/ping

Execute a ping test against a target host from specified locations

POST

/traceroute

Run a traceroute to map the network path to a destination

POST

/dns/lookup

Query DNS records for a domain with specified record type

POST

/port/check

Check if a TCP or UDP port is open and measure connection time

GET

/ssl/validate

Validate SSL certificate for an HTTPS endpoint

Why Jentic?

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

Credential isolation

Ping.ie 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 'run a traceroute' or 'check SSL certificate' and Jentic returns the matching Ping.ie operation along with its input schema.

Time to first call

Direct Ping.ie integration: several hours to wire auth, handle multi-location responses, and parse diagnostic output formats. Through Jentic: under 15 minutes to search, load, and execute.

FAQs

Specific to using Ping.ie Network Diagnostics API through Jentic.

Why is there no official OpenAPI spec for Ping.ie API?

Ping.ie does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ping.ie 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 Ping.ie API use?

Ping.ie 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 run ping tests from multiple geographic locations?

Yes. The POST /ping endpoint accepts a locations array parameter that lets you specify probe points such as Dublin, London, New York, Singapore, and others. The response includes per-location latency metrics in a single call.

How do I check DNS propagation after updating records?

Use POST /dns/lookup with the domain and record type (A, AAAA, MX, etc.). The API queries from multiple DNS resolvers and returns the results showing whether your changes have propagated globally.

What SSL certificate details does the API return?

GET /ssl/validate returns the certificate chain, issuer, subject, validity dates, signature algorithm, key size, supported cipher suites, and any chain validation errors. This covers everything needed for security audits and expiration monitoring.

Can I update a monitor's check interval without losing history?

Yes. PUT /monitors/{monitorId} updates the monitor configuration in place — its identifier and accumulated check history are preserved while you change the interval, target URL, or probe locations.

Ping.ie Network Diagnostics API

Connect the Ping.ie Network Diagnostics API to your agent

Capabilities

Start building with Ping.ie Network Diagnostics API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs