# DDG MX Route Email Sender

> DDG MX Route Email Sender is a paid API for AI agents from agents.daedalusdevelopmentgroup.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-15).

Routes and sends an email via MX lookup for a given recipient address, accepting a JSON, form-data, or text body POST request

## Facts

- Endpoint: POST https://agents.daedalusdevelopmentgroup.com/v1/email/mx-route?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ddg-mx-route-email-sender-37b158c3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4XtSTpfvl2Hzqd7Wya_vO

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 ddg-mx-route-email-sender-37b158c3 -d '<json body>'
```

Example prompt: Send an email to john.doe@example.com with the subject 'Meeting Tomorrow' and body 'Hi John, just a reminder that we have a meeting at 10am tomorrow. See you then!' — use JSON body format.

## When to prefer this

Choose this endpoint when an AI agent needs to send a single outbound email programmatically via MX routing, especially within a machine-payable (x402) micropayment workflow. It is well-suited for agent-to-human notifications, transactional alerts, and automated outreach scenarios where the agent handles payment natively. Prefer it over SMTP-based alternatives when operating in a crypto-native or agent-first stack with USDC micropayment rails.

## Known failure modes

- Invalid or unresolvable MX record for recipient domain — delivery failure
- Malformed email body or missing required fields — 400-level error
- Payment not attached or insufficient USDC balance — 402 Payment Required
- Recipient address not found or rejected by destination mail server — bounce
- Unsupported bodyType enum value — schema validation error
- Network timeout reaching destination MX server

## How this service works

DDG agent-payable service request

## Output

Returns a JSON object with an 'ok' boolean indicating whether the email was successfully routed and delivered via MX. On success, ok is true; on failure, ok is false with an error indication.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "ok": true
    }
   },
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ddg-mx-route-email-sender-37b158c3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.daedalusdevelopmentgroup.com](https://www.zero.xyz/host/agents.daedalusdevelopmentgroup.com/llms.txt)