# DNS vs HTTP Consistency Change Watch

> DNS vs HTTP Consistency Change Watch is a paid API for AI agents from intel.rallylive.ca, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Runs a DNS-vs-HTTP consistency check for a domain, compares it against the previous result (stored 90 days), and returns whether anything changed, exactly which fields changed with before/after values, and the last-seen timestamp.

## Facts

- Endpoint: GET https://intel.rallylive.ca/watch/monitor/dns-vs-http
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dns-vs-http-consistency-change-watch-b63d98d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KoOIAHoFWS47qa8UB1Ne4

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 dns-vs-http-consistency-change-watch-b63d98d6
```

Example prompt: Keep an eye on whether DNS and HTTP are consistent for acme.com — run the check now and tell me if anything changed since the last time you checked, including exactly which fields are different.

## When to prefer this

Choose this endpoint when you need to detect changes in DNS-vs-HTTP consistency over time rather than just seeing the current state. It is ideal for scheduled monitoring workflows where you want to be alerted only when something actually changes, with field-level before/after diffs, rather than parsing raw check results yourself. Prefer it over a one-shot consistency check when you need historical comparison and drift detection built in.

## Known failure modes

- Domain not reachable via HTTP — may return error or incomplete consistency result
- No prior result stored (first call for domain) — 'changed' flag may be undefined or false with no diff
- Domain does not exist in DNS — DNS lookup failure propagated in result
- Payment not fulfilled — 402 response, check not executed
- Stale prior result if more than 90 days have elapsed — treated as first-time check

## How this service works

Change watch for dns http consistency: runs the check and compares it with the result from your previous call for the same domain (kept 90 days), returning the current answer, changed true/false, exactly which fields changed with before/after values, and when it was last seen. Call it on a schedule to be told when dns vs http consistency changes. $0.01 per check.

## Output

Returns the current DNS-vs-HTTP consistency check result, a boolean 'changed' flag indicating whether it differs from the previous call for the same domain, a field-level diff listing exactly which fields changed with their before and after values, and the timestamp of when the previous result was last seen. Previous results are retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dns-vs-http-consistency-change-watch-b63d98d6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.rallylive.ca](https://www.zero.xyz/host/intel.rallylive.ca/llms.txt)