# x402-tools HTTP Check

> x402-tools HTTP Check is a paid API for AI agents from x402.nichospt.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Probes a public HTTP/HTTPS URL and returns status, latency, content type, and redirect chain information.

## Facts

- Endpoint: POST https://x402.nichospt.net/http-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-tools-http-check-03edc09f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dl406aFRs6Ip_yR-UbBnV

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 x402-tools-http-check-03edc09f -d '<json body>'
```

Example prompt: Can you check if https://example.com is up and responding, and tell me the status code, how long it took, and whether it redirected anywhere — use a HEAD request and follow any redirects?

## When to prefer this

Use this endpoint when you need a quick, paid-per-call HTTP availability check with latency and redirect chain data for a single public URL. Prefer it over free monitoring tools when running inside an x402-enabled agent payment flow that already handles USDC micropayments automatically.

## Known failure modes

- URL is unreachable or DNS fails — ok: false with error message
- Non-public/private IP URL rejected
- More than 5 redirects causes failure
- Malformed URL input returns validation error
- Payment not settled in USDC causes 402 rejection before processing

## How this service works

Pay-per-call utility APIs for AI agents, settled in USDC via the x402 protocol.

## Output

A JSON object with: 'ok' (boolean), 'url' (original URL), 'status' (HTTP status code), 'final_url' (after redirects), 'latency_ms' (response time in milliseconds), 'content_type', 'content_length', and 'redirect_chain' (array of intermediate URLs).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Public http(s) URL to probe"
  },
  "method": {
   "enum": [
    "GET",
    "HEAD"
   ],
   "type": "string",
   "default": "HEAD"
  },
  "follow_redirects": {
   "type": "boolean",
   "default": true,
   "description": "Follow up to 5 redirects"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "url": "https://example.com",
  "status": 200,
  "final_url": "https://example.com",
  "latency_ms": 142,
  "content_type": "text/html; charset=UTF-8",
  "content_length": 1256,
  "redirect_chain": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-tools-http-check-03edc09f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.nichospt.net](https://www.zero.xyz/host/x402.nichospt.net/llms.txt)