# Webwache HTTP Status Change Monitor Plan

> Webwache HTTP Status Change Monitor Plan is a paid API for AI agents from webwache.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-11-18).

Passively fetches and evaluates the current HTTP status code of a target URL, returning observation, threshold, verdict, evidence source, and monitoring plan details for change detection.

## Facts

- Endpoint: POST https://webwache.halowerk.com/v1/status-change-monitor?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webwache-http-status-change-monitor-plan-c3f6ea83
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DK4eTJpDAkRZNBTwM-lvh

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 webwache-http-status-change-monitor-plan-c3f6ea83 -d '<json body>'
```

Example prompt: Can you set up an HTTP status change monitor plan for https://example.com and check whether its status code has changed from the baseline I captured last week?

## When to prefer this

Choose this endpoint when you need to passively detect HTTP status code changes on a public URL as part of a recurring monitoring plan, especially when you already have a baseline snapshot and want a verdict on drift. Prefer it over generic uptime tools when you need structured evidence, threshold evaluation, and a plan-oriented action recommendation rather than a simple ping.

## Known failure modes

- Target URL is unreachable or times out — no observation returned
- Invalid or malformed URL provided — validation error
- Target returns no HTTP response (network-level block) — observation unavailable
- Baseline object malformed — comparison skipped or error returned
- Rate limiting or payment failure — 402 or 429 response

## How this service works

HTTP status change monitor plan fetches current public evidence from the supplied target and evaluates the documented criterion. It returns the observation, threshold, verdict, exact evidence source, limitations and a mode-specific action. The check is passive: no login attempt, payload injection, exploit, purchase, form submission or load test is performed.

## Output

Returns the current observed HTTP status code, the documented threshold or expected value, a pass/fail verdict, the exact evidence source URL, any limitations of the passive check, and a mode-specific monitoring plan action — all without performing any login, form submission, or intrusive testing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "target": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 3,
   "description": "Public HTTP(S) URL or domain to inspect. A bare domain is normalized to HTTPS."
  },
  "context": {
   "type": "object",
   "description": "Optional non-secret correlation labels returned unchanged only in the request lifecycle.",
   "maxProperties": 12,
   "additionalProperties": {
    "type": [
     "string",
     "number",
     "boolean",
     "null"
    ]
   }
  },
  "baseline": {
   "type": [
    "object",
    "null"
   ],
   "description": "Optional baseline returned by a previous snapshot call.",
   "additionalProperties": true
  },
  "compare_url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 3,
   "description": "Optional public comparison URL. Used by change and monitoring services."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/webwache-http-status-change-monitor-plan-c3f6ea83/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from webwache.halowerk.com](https://www.zero.xyz/host/webwache.halowerk.com/llms.txt)
