# Domain Intel — MX Google Workspace Check

> Domain Intel — MX Google Workspace 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-12).

Checks whether a domain's MX records are configured for Google Workspace, optionally comparing against a baseline snapshot.

## Facts

- Endpoint: POST https://dns.halowerk.com/domain/articles/mx-google-workspace?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/domain-intel-mx-google-workspace-check-28e61408
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vUO5KayilCy2bBWimbGJS

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-google-workspace-check-28e61408 -d '<json body>'
```

Example prompt: Check if acme.com has its MX records set up for Google Workspace — and compare it against this baseline I recorded last week: exchange='aspmx.l.google.com' with priority 1, observed at '2024-06-01T00:00:00Z'.

## When to prefer this

Choose this endpoint when you need to specifically determine if a domain's MX records are configured for Google Workspace, especially when you want to compare current DNS state against a known historical baseline. It is ideal for no-signup, pay-per-call use cases where you don't want to maintain an API key or subscription — just pay $0.009 USDC per call via x402.

## Known failure modes

- Domain not found or unresolvable — returns error or empty record set
- Malformed domain string exceeding 253 characters — validation error
- Baseline mismatch in required fields causes schema rejection
- Payment failure via x402 protocol blocks the call
- Rate limiting or upstream DNS timeout causes delayed or failed response

## 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 MX record details for the queried domain and an assessment of whether those records match Google Workspace configuration patterns, plus a diff if a baseline snapshot was provided.

## 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-google-workspace-check-28e61408/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)