# AI Rook Email Validate

> AI Rook Email Validate is a paid API for AI agents from agents.ai-rook.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Validates an email address by checking syntax, domain existence, and MX record presence

## Facts

- Endpoint: GET https://agents.ai-rook.com/api/email-validate
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ai-rook-email-validate-d0a09e97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_utFrEF9xreGRFXesHFMgk

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 ai-rook-email-validate-d0a09e97
```

Example prompt: Can you check if user@example.com is a valid, deliverable email address — verify the syntax is correct and that the domain actually has mail servers set up?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call email validation with no API key or signup, paying $0.002 USDC per check. Ideal for AI agents that need to verify email deliverability on-the-fly without maintaining a subscription. Choose this over heavyweight validation services when you need MX record checking plus syntax validation in a single call via x402 micropayment on Base.

## Known failure modes

- Invalid or malformed email input returns syntax_ok false
- Non-existent domain returns mx_found false and valid false
- Network timeout when looking up MX records
- Payment failure via x402 if USDC balance is insufficient on Base mainnet
- Rate limiting or blocked requests if called too rapidly

## How this service works

Email validation — syntax check plus live MX record DNS lookup to confirm deliverability.

## Output

Returns a JSON object with the original email, a boolean 'valid' flag, the parsed domain, whether MX records were found (mx_found), and whether the syntax is correct (syntax_ok).

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "email": "user@example.com",
  "valid": true,
  "domain": "example.com",
  "mx_found": true,
  "syntax_ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ai-rook-email-validate-d0a09e97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.ai-rook.com](https://www.zero.xyz/host/agents.ai-rook.com/llms.txt)