# Webwache Title Change Comparison

> Webwache Title 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-16).

Passively fetches and compares the HTML title tag of a target URL against a baseline or comparison URL, returning the observation, verdict, and evidence details.

## Facts

- Endpoint: POST https://webwache.halowerk.com/v1/title-change-compare?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/webwache-title-change-comparison-3da95871
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8kYYmig7rxgNoCwgdTlUI

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-title-change-comparison-3da95871 -d '<json body>'
```

Example prompt: Check if the title tag on https://example.com has changed compared to https://staging.example.com — give me the verdict, what the titles actually say, and any evidence.

## When to prefer this

Use this endpoint when you need a lightweight, passive check on whether an HTML page's title tag has changed between two states — such as during CI/CD deployments, SEO audits, or competitive monitoring. Prefer it over full content-hash comparisons when you only care about the title field specifically, and over manual checks when you need a structured verdict with evidence sourcing.

## Known failure modes

- Target URL is unreachable or returns a non-2xx status, resulting in an error observation
- Target has no title tag, returning an empty evidence value
- Baseline is null or malformed, causing comparison to fall back to snapshot-only mode
- Rate limiting or bot-protection on target blocks the passive fetch
- Returned verdict may be stale if target uses aggressive caching

## How this service works

Title 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 title tag value(s), whether a change was detected (verdict), the threshold used for evaluation, the exact evidence source URL, any limitations of the passive check, and a recommended action based on the monitoring mode. No authentication, form submission, or exploits are performed.

## 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-title-change-comparison-3da95871/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)
