# Webwache Robots Policy Change Monitor

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

Passively fetches and evaluates a target site's robots.txt to detect policy changes, returning observation, verdict, evidence source, and recommended action.

## Facts

- Endpoint: POST https://webwache.halowerk.com/v1/robots-change-monitor?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-robots-policy-change-monitor-0b8c8f96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5EhRMDGiky8k6ZHuDyi9D

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-robots-policy-change-monitor-0b8c8f96 -d '<json body>'
```

Example prompt: Check whether the robots.txt file at https://example.com has changed since my last snapshot — compare it against my baseline and tell me if anything is different, what the verdict is, and what I should do next.

## When to prefer this

Use this endpoint when you need a lightweight, passive, single-call check on whether a site's robots.txt policy has changed, especially in an agentic monitoring loop or before initiating a web crawl. Prefer it over full-page content hashing endpoints when you specifically care about crawl access rules rather than general content drift.

## Known failure modes

- Target URL is unreachable or returns a non-200 status — endpoint reports evidence unavailable
- robots.txt does not exist at the target — observation notes absence
- Malformed or oversized robots.txt causes parsing issues — limitation noted in response
- Comparison URL is inaccessible — comparison evidence flagged as unavailable
- Rate limiting or firewall blocks the passive fetch — limitation returned in response

## How this service works

Robots policy 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 summarizing what was found in the robots.txt, a threshold and verdict indicating whether a change was detected, the exact evidence source URL, any limitations of the passive check, and a mode-specific recommended action. No login, form submission, or active exploit is 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-robots-policy-change-monitor-0b8c8f96/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)
