# WebberSites Ping — HTTP Liveness Check

> WebberSites Ping — HTTP Liveness Check is a paid API for AI agents from api.webbersites.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Sends a single GET request to any public URL and returns up/down status, HTTP status code, and latency in milliseconds

## Facts

- Endpoint: GET https://api.webbersites.com/api/ping
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webbersites-ping-http-liveness-check-88f939ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6ngarNNv1Xuz9B1MNlfFl

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 webbersites-ping-http-liveness-check-88f939ef
```

Example prompt: Is https://myapp.example.com up right now, and how fast is it responding?

## When to prefer this

Use this endpoint for high-frequency, lightweight liveness polling where you only need up/down, status code, and latency. It does not follow redirects (they are reported as-is) and does not return headers or TLS details. Step up to /api/uptime for redirect-following and headers, or /api/uptime/report for full timing, TLS, and CDN analysis. Ideal for tight monitoring loops where cost and speed matter most at $0.001 per call.

## Known failure modes

- Target URL is unreachable (DNS failure, timeout, TLS error, connection refused) — returns up: false with an error string describing the failure type
- Invalid or malformed URL supplied — likely returns an error response
- Target returns HTTP 500+ — counted as down, status code still returned
- Network timeout from the checker's side — error field set to 'timeout'

## How this service works

Cheapest liveness ping: ONE request to any public URL — is anything answering, and how fast? Returns up/down, HTTP status, and latency in ms. Any HTTP response below 500 counts as up; redirects are reported, not followed. High-frequency monitoring loops belong here; step up to /api/uptime for redirect following and headers, /api/uptime/report for the full timing/TLS/CDN report.

## Output

Returns a JSON object with: 'up' (boolean indicating if server responded with HTTP < 500), 'status' (HTTP status code), 'latency_ms' (round-trip time in milliseconds), 'url' (the pinged URL), 'checked_at' (ISO timestamp), and 'error' (string describing failure reason — e.g. timeout, dns, tls, connection refused — when no response is received).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "description": "Public http(s) URL to ping, e.g. https://example.com"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "up": {
       "type": "boolean"
      },
      "url": {
       "type": "string"
      },
      "error": {
       "type": "string",
       "description": "when no response: timeout, dns, tls, connection refused…"
      },
      "status": {
       "type": "number"
      },
      "checked_at": {
       "type": "string"
      },
      "latency_ms": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "up": true,
  "url": "https://example.com",
  "status": 200,
  "checked_at": "2026-07-09T00:00:00.000Z",
  "latency_ms": 87
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webbersites-ping-http-liveness-check-88f939ef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.webbersites.com](https://www.zero.xyz/host/api.webbersites.com/llms.txt)