# Webwache Security Header Change Monitor

> Webwache Security Header Change Monitor 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-17).

Passively fetches and evaluates security headers from a target URL to detect changes, assess compliance against documented criteria, and produce a verdict with evidence and recommended actions.

## Facts

- Endpoint: POST https://webwache.halowerk.com/v1/security-header-change-monitor?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webwache-security-header-change-monitor-e2a6ffaa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nASA2edfmffLDRit89ED-

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-security-header-change-monitor-e2a6ffaa -d '<json body>'
```

Example prompt: Can you check https://example.com and tell me whether its security headers have changed compared to this baseline snapshot I have — give me the verdict, the exact evidence, and what I should do about it?

## When to prefer this

Use this endpoint when you need passive, non-intrusive monitoring of security header changes on a public-facing URL — especially for scheduled drift detection, pre/post-deployment audits, or compliance verification. Prefer it over active scanners when you must avoid any form of login attempt, payload injection, or load generation. It is ideal for recurring monitoring workflows where a baseline snapshot from a prior call is available for comparison.

## Known failure modes

- Target URL is unreachable or returns a non-200 status — check will fail with an error or empty evidence
- Baseline object is malformed or incompatible — comparison may be skipped or produce an inconclusive verdict
- Target uses HTTPS with an invalid certificate — passive fetch may fail depending on enforcement
- Target URL behind authentication walls — passive check cannot retrieve headers requiring login
- Rate limits or bot-blocking on the target site may cause incomplete header retrieval

## How this service works

Security header 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 an observation describing the current state of security headers, the threshold or criterion evaluated, a pass/fail/changed verdict, the exact evidence source (URL and response data), any limitations of the passive check, and a mode-specific recommended action — all without performing any login, payload injection, or active exploit.

## 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-security-header-change-monitor-e2a6ffaa/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)
