# MX Record Lookup Change Watch

> MX Record Lookup 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).

Monitors MX record lookups for a domain on a schedule, returning the current result, whether it changed, which fields changed with before/after values, and when last seen.

## Facts

- Endpoint: GET https://intel.rallylive.ca/watch/mx-lookup
- 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/mx-record-lookup-change-watch-1fd041c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hzrh5WheIUVjeC9Iaim_p

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 mx-record-lookup-change-watch-1fd041c1
```

Example prompt: Keep watching the MX records for example.com and let me know if anything changes — compare the current records against the last snapshot and tell me exactly which fields changed and what they were before and after.

## When to prefer this

Use this endpoint when you need scheduled or event-driven monitoring of MX record changes for a domain, rather than just a one-off lookup. It is ideal for detecting email infrastructure migrations, unauthorized changes, or phishing domain activity over time, because it stores the previous result for 90 days and returns a structured diff of what changed. Prefer this over a plain MX lookup endpoint when you need change detection semantics built in.

## Known failure modes

- Domain not found or does not resolve — returns an error or empty MX result
- No previous snapshot exists (first call) — 'changed' will be false or indeterminate with no before/after diff
- Domain parameter missing — request validation error
- DNS resolution timeout — lookup may fail transiently
- Payment not included or insufficient — x402 payment required error

## How this service works

Change watch for mx record lookup: 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 mx record lookup changes. $0.01 per check.

## Output

Returns the current MX record lookup result for the domain, a boolean indicating whether it changed since the previous call (retained for 90 days), an enumeration of exactly which fields changed with before and after values, and the timestamp of when the records were last seen.

## 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/mx-record-lookup-change-watch-1fd041c1/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)