# Domain Intel MX Diff — Halowerk x402

> Domain Intel MX Diff — Halowerk x402 is a paid API for AI agents from dns.halowerk.com, paid per call via x402, $0.009/call, status unknown (last checked 2026-10-13).

Given a domain and an optional baseline of previously observed MX records, returns current MX records and highlights changes for the all-inkl mail platform.

## Facts

- Endpoint: POST https://dns.halowerk.com/domain/articles/mx-all-inkl?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/domain-intel-mx-diff-halowerk-x402-4a931c85
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mneadIkYlgLS0H08wbkjJ

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 domain-intel-mx-diff-halowerk-x402-4a931c85 -d '<json body>'
```

Example prompt: Check the current MX records for example.com and compare them against the baseline I recorded last week: mail.example.com at priority 10 and backup.example.com at priority 20 — tell me if anything has changed.

## When to prefer this

Choose this endpoint when you need lightweight, pay-as-you-go MX record lookups with built-in change detection against a known baseline — especially useful for monitoring pipelines, security audits, or agent workflows where you want no signup overhead and per-call USDC micropayments via x402. Prefer it over full DNS-suite endpoints when MX diff is the primary concern.

## Known failure modes

- Domain not found or does not exist — DNS NXDOMAIN response
- Domain has no MX records — empty records array returned
- Malformed domain input exceeding 253 characters — validation error
- Payment not received or x402 handshake failure — 402 response
- Baseline schema invalid or missing required fields — input validation error
- DNS timeout or upstream resolver failure — transient error

## How this service works

Domain in, WHOIS, DNS, mail policy, TLS certificate and subdomains out. Pay per call in USDC over x402. No signup, no API key.

## Output

Returns the current MX records for the domain (exchange hostname and priority for each record) and, when a baseline is supplied, highlights added, removed, or changed records relative to the previously observed state and timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string",
   "maxLength": 253
  },
  "baseline": {
   "type": "object",
   "required": [
    "domain",
    "observed_at",
    "records"
   ],
   "properties": {
    "domain": {
     "type": "string",
     "maxLength": 253
    },
    "records": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "exchange",
       "priority"
      ],
      "properties": {
       "exchange": {
        "type": "string",
        "maxLength": 254
       },
       "priority": {
        "type": "integer",
        "maximum": 65535,
        "minimum": 0
       }
      },
      "additionalProperties": false
     },
     "maxItems": 50
    },
    "observed_at": {
     "type": "string",
     "maxLength": 40
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/domain-intel-mx-diff-halowerk-x402-4a931c85/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dns.halowerk.com](https://www.zero.xyz/host/dns.halowerk.com/llms.txt)