# ISHOB Ping Status — URL Health & SSL Checker

> ISHOB Ping Status — URL Health & SSL Checker is a paid API for AI agents from api.ishob.com, paid per call via x402, $0.0002/call, status unknown (last checked 2026-10-14).

Checks whether a given URL is reachable (up/down), returns HTTP status code, SSL certificate validity, redirect chain, and response time in milliseconds.

## Facts

- Endpoint: POST https://api.ishob.com/v1/ping-status?utm_source=zero.xyz
- Price: $0.0002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ishob-ping-status-url-health-ssl-checker-1ae2f385
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IK6fuTUxdOlw2VbIXXVJe

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ishob-ping-status-url-health-ssl-checker-1ae2f385 -d '<json body>'
```

Example prompt: Can you check if https://mystore.example.com is up right now, verify the SSL certificate is valid, and tell me how many days until it expires? Use a GET request and follow any redirects.

## When to prefer this

Choose this endpoint when you need a lightweight, real-time check of a URL's availability, HTTP status, SSL certificate health, and response latency in a single call — especially within an autonomous agent workflow that needs no API key and supports x402 micropayment-per-call billing. Prefer this over full synthetic monitoring platforms when you need ad-hoc, on-demand checks rather than scheduled polling.

## Known failure modes

- URL unreachable or DNS resolution failure — up: false, no status code returned
- SSL verification failure — ssl.verified: false with no valid_until
- Invalid URI format — input validation error
- Timeout on slow or unresponsive hosts — response_time_ms may be high or missing
- Non-200 status codes returned without error — up may still be true but status reflects actual HTTP response

## How this service works

36 MCP tools &amp; x402 pay-per-call APIs for AI agents: crypto risk, web extraction, screenshots, agent alarms, weather, company data. No API key.

## Output

A JSON object indicating whether the URL is up (boolean), the HTTP status code returned, SSL certificate details (verified status, expiry date, days remaining), an array of any redirect URLs followed, and the total response time in milliseconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "maxLength": 2048
  },
  "method": {
   "enum": [
    "HEAD",
    "GET"
   ],
   "type": "string",
   "default": "HEAD"
  },
  "check_ssl": {
   "type": "boolean",
   "default": true
  },
  "follow_redirects": {
   "type": "boolean",
   "default": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "up": true,
  "ssl": {
   "verified": true,
   "valid_until": "2026-12-25T23:59:59+00:00",
   "days_remaining": 77.7
  },
  "status": 200,
  "redirects": [],
  "response_time_ms": 142
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ishob-ping-status-url-health-ssl-checker-1ae2f385/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ishob.com](https://www.zero.xyz/host/api.ishob.com/llms.txt)