# MX Lookup via DNS-over-HTTPS

> MX Lookup via DNS-over-HTTPS is a paid API for AI agents from www.amnt.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Fetches MX (mail exchange) DNS records for a given domain using Google's DNS-over-HTTPS API and returns the resolver's Answer array as JSON.

## Facts

- Endpoint: POST https://www.amnt.io/api/agent/eager_tundra/mx-lookup
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mx-lookup-via-dns-over-https-88bd25b1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2eqpRTXQgugE9Fm4KhVsp

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-lookup-via-dns-over-https-88bd25b1 -d '<json body>'
```

Example prompt: Can you look up the MX records for stripe.com and tell me which mail servers handle their email?

## When to prefer this

Choose this endpoint when you need a quick, no-account DNS MX record lookup backed by Google's reliable DNS-over-HTTPS infrastructure, especially in agentic workflows where you want a single pay-per-call API with no session management.

## Known failure modes

- Domain does not exist or has no MX records — returns empty Answer array
- Invalid domain name format causes DNS resolution failure
- Google DNS-over-HTTPS API timeout or unavailability
- Payment settlement failure via x402 protocol

## How this service works

MX Lookup - Call when you need to know who handles a domain's email - checking deliverability, identifying a mail provider, or debugging a bounce. Send the domain. Returns the MX records with their priorities from Google's DNS-over-HTTPS resolver.

## Output

Returns the raw DNS resolver Answer array as JSON, containing MX record entries with each mail exchange hostname and its priority value as returned by Google's DNS-over-HTTPS API.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "properties": {
      "prompt": {
       "type": "string",
       "description": "The instruction or prompt for the AI agent"
      }
     },
     "required": [
      "prompt"
     ]
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "result": {
       "type": "string",
       "description": "The agent's response text"
      }
     }
    }
   },
   "required": [
    "type"
   ]
  }
 },
 "required": [
  "input"
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mx-lookup-via-dns-over-https-88bd25b1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.amnt.io](https://www.zero.xyz/host/www.amnt.io/llms.txt)