# Webwache H1 Change Comparison

> Webwache H1 Change Comparison 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).

Fetches the primary H1 heading from a target URL and compares it against a baseline or comparison URL to detect and report changes.

## Facts

- Endpoint: POST https://webwache.halowerk.com/v1/h1-change-compare?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-h1-change-comparison-c023d732
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_56VND_e6Zq75-ZQJ0ZvsH

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-h1-change-comparison-c023d732 -d '<json body>'
```

Example prompt: Check whether the main H1 heading on https://example.com has changed compared to https://old.example.com and tell me what the current heading is, whether it's different, and any limitations you found.

## When to prefer this

Use this endpoint when you specifically need to track or compare the primary H1 heading of a webpage — for SEO auditing, A/B content monitoring, or detecting unauthorized heading changes — without triggering logins, form submissions, or any active site interaction. Prefer this over generic content hash comparisons when you need heading-level granularity rather than full-page diff.

## Known failure modes

- Target URL is unreachable or returns a non-2xx status, resulting in an error observation
- Page has no H1 element, returning an empty or null heading observation
- Comparison URL is inaccessible, preventing a valid comparison
- Malformed or non-HTTP(S) URL input causes validation failure
- Rate limiting or bot-blocking on the target site returns incomplete evidence
- Baseline object is malformed or incompatible, causing comparison to fall back to raw fetch

## How this service works

Primary heading change comparison 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 observed H1 heading content from the target, a comparison verdict (changed or unchanged), the threshold or criterion used, the exact evidence source URL, any limitations encountered during the passive fetch, and a mode-specific recommended action.

## 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-h1-change-comparison-c023d732/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)
