# Domain Intel MX Records — Amazon SES Baseline Check

> Domain Intel MX Records — Amazon SES Baseline Check 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).

Analyzes a domain's MX records and compares them against an Amazon SES baseline to surface mail policy intelligence.

## Facts

- Endpoint: POST https://dns.halowerk.com/domain/articles/mx-amazon-ses?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-records-amazon-ses-baseline-check-87e6e86a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Bfcm2p1kbmWt2nwD9RfAm

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-records-amazon-ses-baseline-check-87e6e86a -d '<json body>'
```

Example prompt: Look up the MX records for example.com and compare them against this Amazon SES baseline I observed last week — exchanges inbound-smtp.us-east-1.amazonaws.com at priority 10, observed_at 2024-06-01T00:00:00Z — and tell me if anything has changed.

## When to prefer this

Choose this endpoint when you need to compare a domain's live MX records specifically against an Amazon SES baseline you previously observed, especially when monitoring for configuration drift or verifying SES adoption without requiring an API key or subscription. Ideal for pay-per-use, no-registration workflows via x402.

## Known failure modes

- Domain not found or invalid — DNS lookup failure returns error
- Baseline schema missing required fields (domain, observed_at, records) — validation error
- Domain string exceeds 253 characters — input rejected
- MX records array exceeds 50 items — schema violation
- Payment not included or insufficient USDC — x402 payment required error
- Upstream DNS resolver unavailable — transient lookup failure

## 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 current MX record details for the domain along with a comparison against the provided Amazon SES baseline, highlighting matches, mismatches, or changes since the baseline observation 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-records-amazon-ses-baseline-check-87e6e86a/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)