# how.is Site Status Checker

> how.is Site Status Checker is a paid API for AI agents from how.is, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-31).

Performs a live multi-signal check on up to 10 URLs, returning HTTP status, latency, DNS resolve time, resolved IP, TTL, nameservers, TLS certificate days remaining, and server info.

## Facts

- Endpoint: POST https://how.is/v1/check/site?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/how-is-site-status-checker-5b985a38
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qQBADYCge8etLyCrk5t-s

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 how-is-site-status-checker-5b985a38 -d '<json body>'
```

Example prompt: Can you do a live check on https://example.com and https://api.example.com — I want to see their HTTP status, response latency, DNS resolve time, resolved IP, nameservers, and how many days are left on their TLS certificates?

## When to prefer this

Use this endpoint when you need a live, real-time probe of a URL's actual HTTP reachability, latency, DNS resolution, and TLS certificate status — especially when you need all of these signals in a single call for up to 10 URLs. Prefer it over generic uptime monitors when you need raw DNS and TLS data alongside HTTP status, or when you need an on-demand check rather than scheduled polling. It complements the how.is safety and domain-intelligence endpoints by providing pure infrastructure-layer health signals.

## Known failure modes

- URL is unreachable or returns a non-2xx status — reflected in ok=false and code fields rather than an error
- Invalid or malformed URL submitted — likely a 400-level validation error
- More than 10 URLs submitted — rejected due to maxItems constraint
- DNS resolution failure — dns_ms may be null or error indicated in response
- TLS/cert inspection may fail for HTTP-only sites with no cert — cert_days returns null
- Payment failure on x402 rail — request not processed if micropayment cannot be settled

## How this service works

Live check of one or more URLs: HTTP status, latency, DNS resolve time, resolved IP, TTL, nameservers, TLS days remaining.

## Output

A JSON object keyed by each submitted URL, where each entry contains: ok (boolean reachability), code (HTTP status code), ms (response latency in milliseconds), dns_ms (DNS resolve time in milliseconds), ip (resolved IP address), ttl (DNS TTL), ns (nameservers array), cert_days (TLS certificate days remaining), server (server header value), and ts (timestamp of the check). Also includes a receipt confirming the x402 micropayment of $0.005 USDC.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sites": {
   "type": "array",
   "items": {
    "type": "string",
    "format": "uri"
   },
   "maxItems": 10,
   "description": "Up to 10 http(s):// URLs"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "_shape": "data keyed by URL; each entry has ok, code, ms, dns_ms, ip, ttl, ns, cert_days, server, ts."
  },
  "result": "Site status for the requested subject",
  "receipt": {
   "rail": "x402",
   "tool": "site_status",
   "charge_usd": 0.005,
   "settlement_tx": "0x…"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/how-is-site-status-checker-5b985a38/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from how.is](https://www.zero.xyz/host/how.is/llms.txt)