# Hyrule Cloud MX Jobs – Mail Deliverability Analysis

> Hyrule Cloud MX Jobs – Mail Deliverability Analysis is a paid API for AI agents from cloud.hyrule.host, paid per call via x402, $0.03/call, status down (last checked 2026-09-15).

Submits an asynchronous mail deliverability analysis job for a target domain, returning a job ID and status for the MX/mail infrastructure profile check.

## Facts

- Endpoint: POST https://cloud.hyrule.host/v1/mx/jobs
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hyrule-cloud-mx-jobs-mail-deliverability-analysis-cc112724
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uI0HrUtcCDNINd8L7KMlm

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 hyrule-cloud-mx-jobs-mail-deliverability-analysis-cc112724 -d '<json body>'
```

Example prompt: Run a mail deliverability job on example.com using the mail_delivery profile — I want to know if emails from that domain will land in the inbox or get flagged as spam.

## When to prefer this

Choose this endpoint when you need an asynchronous, comprehensive mail deliverability audit for a domain — especially when you need MX, SPF, DKIM, DMARC, and blacklist checks bundled into one job. Prefer it over synchronous DNS lookups when you want a full mail_delivery profile rather than a single record type. Well-suited for AI agents that pay per request in USDC via x402 and need structured deliverability results to act on.

## Known failure modes

- Invalid or non-existent target domain returns an error or empty results
- Insufficient USDC balance on Base causes payment failure and job not created
- Job may remain in pending/processing status if mail infrastructure is slow to respond
- Malformed profile name causes job rejection
- Rate limiting may occur with rapid repeated submissions

## How this service works

Hyrule Cloud is pay-per-use infrastructure for AI agents on AS215932: IPv6-native compute, outbound requests over Direct, Tor, I2P, or Yggdrasil, BGP/routing intelligence, IP/ASN intelligence, DNS diagnostics, RDAP/WHOIS registry lookups, web and deep TLS checks, mail deliverability, outside-in port reachability, NAT port-forward checks, VoIP/SIP diagnostics. Calls settle in USDC via x402. This endpoint: Paid full mail-delivery diagnostic report (synchronous, results returned inline).

## Output

Returns a JSON object containing a unique job_id (e.g. mxj_a1b2c3d4), the current job status (e.g. 'completed'), the target domain analyzed, the profile used (e.g. 'mail_delivery'), an array of deliverability results, and a created_at timestamp. Results detail MX records, SPF/DKIM/DMARC posture, blacklist presence, and related mail infrastructure signals.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "job_id": "mxj_a1b2c3d4",
  "status": "completed",
  "target": "example.com",
  "profile": "mail_delivery",
  "results": [],
  "created_at": "2026-07-15T00:00:00Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hyrule-cloud-mx-jobs-mail-deliverability-analysis-cc112724/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cloud.hyrule.host](https://www.zero.xyz/host/cloud.hyrule.host/llms.txt)